Jamf Docs MCP Server

Get Jamf Documentation Article

jamf_docs_get_article

Read-onlyIdempotent

Retrieve any Jamf documentation article as clean, readable text by URL or map and content IDs. Preview with a summary, pull one section, or limit response size.

Instructions

Retrieve the full content of a specific Jamf documentation article.

This tool fetches and parses a Jamf documentation article, converting it to a clean, readable format. Works with any article from learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com.

Address the article either by url, or by the mapId + contentId pair that search results and TOC entries carry. One of the two is required. Passing both, as a search result allows, is fine: on learn.jamf.com the pair decides which article is fetched, and the result's url is that article's own address (a note says so if the url you passed does not match it). A concepts.jamf.com or support.jamf.com url is fetched by url, and a note says the pair was ignored. A support.jamf.com collection url, which a TOC lists each subcollection by, returns the collection's list of articles.

Args:

url (string, optional): Full https:// URL of the article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com, at most 2048 characters. Required unless mapId and contentId are given
mapId (string, optional): Fluid Topics map ID, from a search result or a TOC. Use with contentId, instead of url or alongside it
contentId (string, optional): Fluid Topics content ID, from a search result or a TOC entry. Use with mapId, instead of url or alongside it
language (string, optional): Documentation language/locale. Overrides the locale in url, which is used when this is omitted. A learn.jamf.com publication Jamf does not publish in it is served in en-US, and a concepts.jamf.com or support.jamf.com page with no edition in it as the url names it, both with a note; contentLocale says which language was served. No effect on a mapId + contentId pair (a map is in one language)
section (string, optional): Extract only a specific section by title or ID (e.g., "Prerequisites", "Configuration")
summaryOnly (boolean, optional): Return only article summary and outline instead of full content (default: false). Token-efficient way to preview an article and its sub-topics
includeRelated (boolean, optional): Include links to related articles (default: false)
maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000)
outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for brief output
responseFormat ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "title": string, "content": string, "url": string, "product": string, "version": string, "contentLocale": string, // the language content is in, where the article says "breadcrumb": string[], "relatedArticles": [...], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "sections": [ { "id": string, "title": string, "level": number, "tokenCount": number } ] }

For Markdown format: The article content with token info and available sections.

Examples:

Get full article: url="https://learn.jamf.com/en-US/bundle/jamf-pro-documentation/page/Computer_Configuration_Profiles.html"
Fetch a search result directly: mapId="...", contentId="..." (both from the result)
Get specific section: url="...", section="Prerequisites"
Limit response size: url="...", maxTokens=2000

Errors:

"Either url or both mapId and contentId must be provided." if neither url nor the full pair is given
"URL must be from learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com" (an input validation error) if url is not https:// on one of those hosts
"URL must not exceed 2048 characters" (an input validation error) if url is longer
"Topic not found", "Cannot resolve bundleId", "Cannot resolve product" or "HTTP 404" if no article is found at that address, with advice on finding it

Note: maxTokens bounds every reply: the article or one section, a summaryOnly outline, a missed section's reply, and any note about how the call was resolved, all counted in tokenInfo.tokenCount. Large articles are intelligently truncated with remaining sections listed, as many as fit; a list cut to fit says how many it left out, and truncated is true. Use the section parameter, at most 200 characters, to retrieve specific sections for long articles. A section that matches no heading is not an error: the reply says 'Section "" not found' and lists the article's sections, or says it has none. Most learn.jamf.com topics have no headings; what the website shows as their sections are sub-topics, which the reply lists with their urls, a matching one first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Full https:// URL of the Jamf documentation article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com, at most 2048 characters. Alternative: use mapId + contentId for direct fetch. One of the two is required.
`mapId`	No	Fluid Topics map ID (from search results or TOC). Use with contentId for direct fetch.
`section`	No	Extract only a specific section by title or ID (e.g., "Prerequisites", "Configuration"), at most 200 characters
`language`	No	Documentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. A learn.jamf.com publication Jamf does not publish in it is served in en-US, and a concepts.jamf.com or support.jamf.com page with no edition in it as the URL names it, both with a note; contentLocale says which language was served. No effect on a mapId + contentId pair, whose map is already in one language. Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN
`contentId`	No	Fluid Topics content ID (from search results or TOC). Use with mapId for direct fetch.
`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
`summaryOnly`	No	Return only article summary and outline instead of full content (token-efficient)
`includeRelated`	No	Include related article links in the response
`responseFormat`	No	Output format: "markdown" for human-readable or "json" for machine-readable	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`mapId`	No
`title`	Yes
`content`	Yes
`product`	No
`version`	No
`sections`	Yes
`contentId`	No
`truncated`	Yes
`breadcrumb`	No
`navigation`	No
`tokenCount`	No
`lastUpdated`	No
`contentLocale`	No
`versionStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv6.0.14Sep 30, 2026

changedInput schema / properties / language / description

Previous value: -"Documentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. Has no effect on concepts.jamf.com or support.jamf.com URLs, or on a mapId + contentId pair, whose map is already in one language. Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN"New value: +"Documentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. A learn.jamf.com publication Jamf does not publish in it is served in en-US, and a concepts.jamf.com or support.jamf.com page with no edition in it as the URL names it, both with a note; contentLocale says which language was served. No effect on a mapId + contentId pair, whose map is already in one language. 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 / section / description

Previous value: -"Extract only a specific section by title or ID (e.g., \"Prerequisites\", \"Configuration\")"New value: +"Extract only a specific section by title or ID (e.g., \"Prerequisites\", \"Configuration\"), at most 200 characters"

addedInput schema / properties / section / maxLength
```
Added value: +200
```

changedInput schema / properties / url / description

Previous value: -"Full https:// URL of the Jamf documentation article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com. Alternative: use mapId + contentId for direct fetch. One of the two is required."New value: +"Full https:// URL of the Jamf documentation article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com, at most 2048 characters. Alternative: use mapId + contentId for direct fetch. One of the two is required."

addedInput schema / properties / url / maxLength
```
Added value: +2048
```

Changed2 schema fields changedv6.0.11Sep 24, 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, it-IT, pt-BR, zh-CN"New value: +"Documentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. Has no effect on concepts.jamf.com or support.jamf.com URLs, or on a mapId + contentId pair, whose map is already in one language. 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 / url / description

Previous value: -"Full URL of the Jamf documentation article. Alternative: use mapId + contentId for direct fetch."New value: +"Full https:// URL of the Jamf documentation article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com. Alternative: use mapId + contentId for direct fetch. One of the two is required."

Changed2 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"
+]

Changed3 schema fields changedv4.3.1Aug 5, 2026

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

addedOutput schema / properties / navigation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "childCount": {
+      "type": "number"
+    },
+    "children": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "parent": {
+      "additionalProperties": false,
+      "properties": {
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "title",
+        "url"
+      ],
+      "type": "object"
+    },
+    "self": {
+      "additionalProperties": false,
+      "properties": {
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "title",
+        "url"
+      ],
+      "type": "object"
+    },
+    "siblingCount": {
+      "type": "number"
+    },
+    "siblings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "self",
+    "siblings",
+    "children",
+    "siblingCount",
+    "childCount"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / versionStatus

Added value: +{
+  "enum": [
+    "latest",
+    "superseded"
+  ],
+  "type": "string"
+}

Changed5 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 / contentId / pattern

Previous value: -"^[a-zA-Z0-9_~\\-]+$"New value: +"^[a-zA-Z0-9_~-]+$"

changedInput schema / properties / mapId / pattern

Previous value: -"^[a-zA-Z0-9_~\\-]+$"New value: +"^[a-zA-Z0-9_~-]+$"

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 / tokenCount
```
Added value: +{
+  "type": "number"
+}
```

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

TDQS

A4.3/5.0

Behavior5/5

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

With annotations already covering readOnly/idempotent/openWorld/non-destructive, the description goes well beyond them: it discloses precedence between url and the id pair on each host, language fallback to en-US with a note and contentLocale, and detailed truncation behavior bounded by maxTokens. It also documents non-error behaviors such as a section that matches no heading, which an agent could not infer otherwise.

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

Conciseness4/5

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

It is front-loaded with purpose and organized into Args/Returns/Errors/Note sections, so it is easy to scan. It is nonetheless long, and the Args block and Returns block largely restate what the schema and output schema already carry, which is redundancy rather than information.

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 a 10-parameter tool with 3 enums and an output schema, the definition covers resolution logic, fallbacks, truncation, error strings, and edge cases (empty section lists, ignored id pairs). An agent has everything needed to call it correctly and interpret the response without opening other tools.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: the resolution precedence of mapId+contentId versus url per host, language override semantics (including why it has no effect on an id pair), and the section-not-found behavior. This is more than the schema conveys, though some param text is duplicated rather than additive.

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

Purpose4/5

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

The description opens with a specific verb and resource ('Retrieve the full content of a specific Jamf documentation article') and clarifies the supported hosts, so the agent knows exactly what this does. It implicitly distinguishes itself from siblings by noting that search results and TOC entries supply the mapId/contentId pair, but it never names a sibling tool or states an explicit boundary against batch_get_articles.

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?

It gives clear routing context: address by `url` or by the `mapId`+`contentId` pair that search results and TOC entries carry, and notes `summaryOnly` as a token-efficient preview path. However, it does not state when to prefer this over `jamf_docs_batch_get_articles` for multiple articles, and offers no explicit exclusions.

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

Deploy Server

Get Jamf Documentation Article

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools