Jamf Docs MCP Server

Get Documentation Table of Contents

jamf_docs_get_toc

Read-onlyIdempotent

Browse the table of contents for any Jamf product or publication to discover available topics before searching or retrieving articles.

Instructions

Get the table of contents for Jamf documentation.

Browse the navigation structure of either a Jamf product or any single Jamf publication - release notes, technical papers, courses, evaluation guides and configuration guides all live on the publication axis rather than the product one. Exactly one of product and publication is required.

Args:

product (string): Product ID - one of: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener
publication (string): Bundle family id of any single publication, e.g. "technical-paper-laps" or "jamf-pro-release-notes". Call jamf_docs_list_products for the available ids
version (string, optional): Specific version (e.g., "11.13.0") or "current" (defaults to latest)
language (string, optional): Documentation language/locale (default: en-US)
page (number, optional): Page number for pagination 1-100 (default: 1)
maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000)
outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for flat list without nested children
responseFormat ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "product": string, "version": string, "mapId": string, // omitted when the map could not be resolved "toc": [...], // each entry carries title, url and contentId "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "pagination": { "page": number, "pageSize": number, "totalPages": number, "totalItems": number, "hasNext": boolean, "hasPrev": boolean }, "truncatedEntry"?: { // only on a page cut to fit; see the Note "title": string, "shownEntries": number, "totalEntries": number, "estimatedTokens": number } }

For Markdown format: A hierarchical list of documentation topics with pagination and token info.

Examples:

Browse Jamf Pro documentation: product="jamf-pro"
Get page 2 of TOC: product="jamf-pro", page=2
Limit response size: product="jamf-pro", maxTokens=2000

Errors:

"Invalid option: expected one of ..." (an input validation error) if product is not a known product ID
'Version "" not found', followed by the available versions, if that version is not published

Note: Use this to discover what topics are available before searching or retrieving specific articles. Large TOCs are paginated by top-level entry: a page holds up to 10 of them, each with everything under it, as many as fit maxTokens, and the next page starts at the first that did not fit. Every top-level entry is on exactly one page, but which page depends on maxTokens, so keep maxTokens the same while paging; the markdown footer names it beside the next page when it is not the default. A top-level entry larger than maxTokens on its own is alone on its page, cut to the entries under it that fit; only that page has tokenInfo.truncated, and truncatedEntry.estimatedTokens is what the whole entry costs. If maxTokens makes more pages than page accepts (100), page 100 offers no next page and paginationNote names a maxTokens that reaches the rest. The response-level mapId and an entry's contentId together form the pair jamf_docs_get_article accepts for a direct fetch. Markdown output shows the mapId only; use responseFormat="json" (or read structuredContent) for the per-entry contentIds. structuredContent also carries what to send back for the next page: productId (or publicationId), version, language (when one was asked for) and maxTokens. The JSON text has no id or language, and has the budget as tokenInfo.maxTokens. structuredContent.entries is the TOC flattened in document order and always carries every descendant; each entry's depth (0 for top level) is what restores the nesting. The markdown is not the same view: outputMode="full" shows that nesting as indentation, while outputMode="compact" lists only the top-level entries and shows no nesting at all.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number for pagination (1-100, default: 1)
`product`	No	Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener
`version`	No	Specific version (e.g. "11.13.0"); defaults to latest
`language`	No	Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN
`maxTokens`	No	Maximum tokens in response (100-50000, default: 5000)
`outputMode`	No	Output detail level: "full" for detailed output or "compact" for brief output	full
`publication`	No	Bundle family id for any Jamf publication, e.g. "technical-paper-laps" or "jamf-pro-release-notes". Use this for the documents that are not one of the products in `product` — release notes, technical papers, courses, evaluation and configuration guides. Exactly one of `product` or `publication` is required. Call jamf_docs_list_products to see the available ids.
`responseFormat`	No	Output format: "markdown" for human-readable or "json" for machine-readable	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`mapId`	No
`entries`	Yes
`hasMore`	Yes
`product`	Yes
`version`	Yes
`language`	No
`maxTokens`	Yes
`productId`	No
`localeNote`	No
`totalPages`	Yes
`versionNote`	No
`totalEntries`	Yes
`publicationId`	No
`paginationNote`	No
`truncatedEntry`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv6.0.12Sep 27, 2026

addedOutput schema / properties / language
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / maxTokens

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / truncatedEntry

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "estimatedTokens": {
+      "type": "number"
+    },
+    "shownEntries": {
+      "type": "number"
+    },
+    "title": {
+      "type": "string"
+    },
+    "totalEntries": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "title",
+    "shownEntries",
+    "totalEntries",
+    "estimatedTokens"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "product",
-  "version",
-  "totalEntries",
-  "page",
-  "totalPages",
-  "hasMore",
-  "entries"
-]New value: +[
+  "product",
+  "version",
+  "totalEntries",
+  "page",
+  "totalPages",
+  "hasMore",
+  "maxTokens",
+  "entries"
+]

Changed11 schema fields changedv5.10.1Sep 8, 2026

changedInput schema / properties / language / description

Previous value: -"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH"New value: +"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN"

changedInput schema / properties / language / enum

Previous value: -[
-  "en-US",
-  "ja-JP",
-  "zh-TW",
-  "de-DE",
-  "es-ES",
-  "fr-FR",
-  "nl-NL",
-  "th-TH"
-]New value: +[
+  "en-US",
+  "ja-JP",
+  "zh-TW",
+  "de-DE",
+  "es-ES",
+  "fr-FR",
+  "nl-NL",
+  "th-TH",
+  "it-IT",
+  "pt-BR",
+  "zh-CN"
+]

changedInput schema / properties / product / description

Previous value: -"Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"New value: +"Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener"

changedInput schema / properties / product / enum

Previous value: -[
-  "jamf-pro",
-  "jamf-school",
-  "jamf-connect",
-  "jamf-protect",
-  "jamf-now",
-  "jamf-safe-internet",
-  "jamf-insights",
-  "jamf-rapididentity",
-  "jamf-trust",
-  "jamf-routines",
-  "self-service-plus",
-  "jamf-app-catalog"
-]New value: +[
+  "jamf-pro",
+  "jamf-school",
+  "jamf-connect",
+  "jamf-protect",
+  "jamf-now",
+  "jamf-safe-internet",
+  "jamf-insights",
+  "jamf-rapididentity",
+  "jamf-trust",
+  "jamf-routines",
+  "self-service-plus",
+  "jamf-app-catalog",
+  "jamf-account",
+  "jamf-security-cloud",
+  "elevate",
+  "composer",
+  "jamf-parent",
+  "jamf-teacher",
+  "jamf-setup-reset",
+  "jamf-assessment",
+  "title-editor",
+  "jamf-infrastructure-manager",
+  "jamf-adcs-connector",
+  "jamf-pki-proxy",
+  "jamf-migrate",
+  "jamf-remote-assist",
+  "jamf-cloud-distribution-service",
+  "healthcare-listener"
+]

addedInput schema / properties / publication

Added value: +{
+  "description": "Bundle family id for any Jamf publication, e.g. \"technical-paper-laps\" or \"jamf-pro-release-notes\". Use this for the documents that are not one of the products in `product` — release notes, technical papers, courses, evaluation and configuration guides. Exactly one of `product` or `publication` is required. Call jamf_docs_list_products to see the available ids.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / version / description

Previous value: -"Specific version (defaults to latest)"New value: +"Specific version (e.g. \"11.13.0\"); defaults to latest"

addedInput schema / properties / version / pattern
```
Added value: +"^(?:current|\\d+(?:\\.\\d+)*)$"
```
removedInput schema / required
```
Removed value: -[
-  "product"
-]
```
addedOutput schema / properties / localeNote
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / publicationId
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "product",
-  "productId",
-  "version",
-  "totalEntries",
-  "page",
-  "totalPages",
-  "hasMore",
-  "entries"
-]New value: +[
+  "product",
+  "version",
+  "totalEntries",
+  "page",
+  "totalPages",
+  "hasMore",
+  "entries"
+]

Changed2 schema fields changedv4.3.1Aug 5, 2026

addedOutput schema / properties / entries / items / properties / depth

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / entries / items / required

Previous value: -[
-  "title",
-  "url"
-]New value: +[
+  "title",
+  "url",
+  "depth"
+]

Changed8 schema fields changedv4.0.6Aug 3, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / product / description

Previous value: -"Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect"New value: +"Product ID: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / mapId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / paginationNote
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / productId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / versionNote
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "product",
-  "version",
-  "totalEntries",
-  "page",
-  "totalPages",
-  "hasMore",
-  "entries"
-]New value: +[
+  "product",
+  "productId",
+  "version",
+  "totalEntries",
+  "page",
+  "totalPages",
+  "hasMore",
+  "entries"
+]

Addedv3.0.34Jun 18, 2026
Removedv3.0.30Jun 16, 2026
First observedv3.0.25May 28, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial operational detail: how pagination splits by top-level entry, that page assignment depends on maxTokens, that changing maxTokens mid-page breaks paging, the single truncated page behavior, the page-100 cap, and the exact error strings for bad product IDs and missing versions. This is well beyond the safety profile the annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading is good and the Note carries the highest-value content, but two full blocks are redundant: the Args list restates every schema property description verbatim, and the Returns section reproduces an entire JSON response shape that the output schema already defines. Roughly half the text duplicates structured data, diluting an otherwise well-organized payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, paginated tool with a rich output schema, the description covers everything an agent needs: axis selection, the mutual-exclusion constraint, paging stability rules, truncation signaling, structuredContent continuation fields, and the mapId/contentId pairing for article fetches. Return values are where they belong, in the output schema, and the Note supplies the cross-call knowledge the schema cannot.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description contributes genuine semantics the schema does not: 'Exactly one of product and publication is required' (the schema marks neither as required, so this constraint is only available here), the meaning of publication as a bundle family for non-product docs, and outputMode='compact' as a flat list without nested children rather than the schema's generic 'brief output'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the table of contents for Jamf documentation') and immediately scopes it: 'Browse the navigation structure of either a Jamf product or any single Jamf publication.' It goes further than any sibling by explaining that release notes, technical papers, courses and guides live on the publication axis, not the product axis, so an agent can select correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: 'Use this to discover what topics are available before searching or retrieving specific articles,' which positions it relative to jamf_docs_search and jamf_docs_get_article. It also points to jamf_docs_list_products for publication ids. It lacks an explicit when-not (e.g., when to skip the TOC and search directly), so it stops short of the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Get Documentation Table of Contents

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools