Get Jamf Documentation Article

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.

Args:

• url (string, optional): Full https:// URL of the article, on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com. 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. No effect on a mapId + contentId pair (a map is in one language) or on concepts.jamf.com or support.jamf.com URLs

• 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, "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

• "Topic not found", "Cannot resolve bundleId" or "HTTP 404" if there is no article at that address

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 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.