Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Get Jamf Documentation Article

jamf_docs_get_article
Read-onlyIdempotent

Retrieve and parse full content from any Jamf documentation article, optionally extracting specific sections or returning summaries for token-efficient previews.

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 docs.jamf.com or learn.jamf.com.

Args:

  • url (string, required): Full URL of the article (must be from docs.jamf.com or learn.jamf.com)

  • 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

  • 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/Configuration_Profiles.html"

  • Get specific section: url="...", section="Prerequisites"

  • Limit response size: url="...", maxTokens=2000

Errors:

  • "Article not found (404)" if the URL returns a 404 error

  • "Invalid URL" if the URL is not from docs.jamf.com or learn.jamf.com

  • "Section not found" if the specified section doesn't exist (will list available sections)

Note: Large articles are intelligently truncated with remaining sections listed. Use the section parameter to retrieve specific sections for long articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull URL of the Jamf documentation article. Alternative: use mapId + contentId for direct fetch.
mapIdNoFluid Topics map ID (from search results or TOC). Use with contentId for direct fetch.
contentIdNoFluid Topics content ID (from search results or TOC). Use with mapId for direct fetch.
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH
sectionNoExtract only a specific section by title or ID (e.g., "Prerequisites", "Configuration")
summaryOnlyNoReturn only article summary and outline instead of full content (token-efficient)
includeRelatedNoInclude related article links in the response
maxTokensNoMaximum tokens in response (100-50000, default: 5000)
outputModeNoOutput detail level: "full" for detailed output or "compact" for brief outputfull
responseFormatNoOutput format: "markdown" for human-readable or "json" for machine-readablemarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
urlYes
contentYes
productNo
versionNo
lastUpdatedNo
breadcrumbNo
mapIdNo
contentIdNo
sectionsYes
truncatedYes
Behavior5/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral details like 'Large articles are intelligently truncated with remaining sections listed' and error states (404, invalid URL, section not found). No contradiction.

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?

The description is well-structured with sections for Args, Returns, Examples, Errors, Note. It front-loads the core purpose but is somewhat lengthy. Could be slightly more concise but remains clear.

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?

Given 10 parameters (none required), an output schema, and sibling tools, the description covers return values, error handling, usage notes, and truncation behavior. Complete for effective agent use.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds value beyond schema: explains 'token-efficient way to preview an article' for summaryOnly, and error conditions. Adds meaning to parameters.

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?

The description clearly states 'Retrieve the full content of a specific Jamf documentation article' with a specific verb and resource. It distinguishes from sibling tools like batch_get and search.

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?

Provides clear usage context: 'Works with any article from docs.jamf.com or learn.jamf.com.' Includes examples and parameter descriptions. Lacks explicit when-not-to-use or alternative comparisons, but sibling tool names are listed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GET-Technology-Inc/jamf-docs-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server