get_content_detail

Vehicle data · Read-only

Fetch the full detail for one content item found via list_content.

Usage

Details include labor times with skill codes, service intervals, notes, and cross-links to related content. Documents referenced by a detail (bulletin PDFs, illustrations) are linked by reference — binary content never travels through a tool result on this surface.

Parameters

Parameter	Type	Required	Description
`baseVehicleId`	positive integer	Yes	The baseVehicleId field from a resolve_vehicle result. NOT the vehicleId (rejected with 400.110052). Example: 22124
`contentType`	"EstimatedWorkTimes" \| "Specifications" \| "TechnicalServiceBulletins" \| "DiagnosticTroubleCodes" \| "ServiceProcedures" \| "WiringDiagrams" \| "Fluids" \| "Parts" \| "MaintenanceSchedules" \| "ComponentLocations" \| "PartVectorIllustrations"	Yes	Which MOTOR content family to query. Example: "TechnicalServiceBulletins"
`applicationId`	positive integer	Yes	ApplicationID from a list_content summary row. Example: 871003

Description advertised to clients

The exact description a fully entitled MCP client discovers — the workflow contracts travel with the tool, so a client with no system prompt still uses it correctly. An account missing a licence for content this tool reaches sees the same text behind a [Licensed content — not enabled on this account] or [Partially available] notice:

Fetch the full detail for one content item found via list_content. The baseVehicleId parameter MUST be the baseVehicleId field from a resolve_vehicle result — NOT the vehicleId, which is rejected with error 400.110052. Details include labor times with skill codes, service intervals, notes, and cross-links to related content. Parts details carry OEM LIST pricing under pricing (oemPartNumber, listPrice, listPriceCents) — the OEM list price, not the shop's sell price. The evaluation sandbox covers model years 2010, 2015, and 2016 ONLY. Empty results for other vehicles are correct behaviour, not an error — tell the user the vehicle is not covered rather than retrying.

Example — One bulletin in full

Captured from the live server, 2026-08-20. Engine attribute block truncated.

Request

{
  "baseVehicleId": 22124,
  "contentType": "TechnicalServiceBulletins",
  "applicationId": 474099311
}

Response

{
  "applicationId": 474099311,
  "contentType": "TechnicalServiceBulletins",
  "detail": {
    "Attributes": {
      "Engines": [
        {
          "Description": "1.8L L4 (R18A1) GAS FI",
          "EngineID": 2913,
          "FuelType": "GAS"
        }
      ],
      "SubModels": [
        {
          "SubModelID": 1609,
          "SubModelName": "LX-S"
        }
      ]
    },
    "TechnicalServiceBulletins": [
      {
        "BaseVehicleID": 22124,
        "Items": [
          {
            "Description": "A/C Leak Detection",
            "Document": {
              "Name": "180064.pdf",
              "Type": "Technical Service Bulletin",
              "DocumentID": 9899934,
              "Format": "application/pdf"
            },
            "Issuer": {
              "ManufacturerID": 39,
              "Name": "Honda",
              "Type": "OE"
            },
            "IssueDate": "2023-12-08T00:00:00",
            "ManufacturerNumber": "07-030",
            "TSBID": 134569,
            "Types": [
              {
                "ID": 6,
                "Type": "Service Bulletin"
              }
            ]
          }
        ],
        "ApplicationID": 474099311
      }
    ]
  },
  "relatedContent": [
    {
      "rel": "TechnicalServiceBulletinsDocument",
      "href": "/v1/Information/Vehicles/Attributes/BaseVehicleID/22124/Content/Documents/Of/TechnicalServiceBulletins/9899934"
    }
  ]
}