Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Get Jamf Documentation Article

jamf_docs_get_article
Read-onlyIdempotent

Fetch and parse Jamf documentation articles. Retrieve full content, specific sections, or concise summaries to answer Jamf-related questions directly.

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:

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

Output Schema

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

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds no contradiction. It further discloses truncation behavior for large articles, error types (404, invalid URL, section not found), and return formats (markdown/json). This goes beyond annotations.

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 clear sections (Purpose, Args, Returns, Examples, Errors, Notes). It is fairly long but each sentence adds value. Front-loaded with main purpose. Could be slightly more concise, but no redundancy.

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?

With 10 parameters, a rich output schema, error handling, examples, and behavior notes (truncation), the description covers all necessary aspects for safe and correct usage. The agent can understand how to use this tool effectively.

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 coverage is 100%, so baseline is 3. The description adds value by explaining parameter use cases (e.g., 'token-efficient way to preview an article' for summaryOnly, default values, and the contrast between url and mapId+contentId). However, much of this is also in the schema descriptions.

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.' The verb 'Retrieve' and resource 'article' are specific. It distinguishes from siblings like jamf_docs_batch_get_articles (batch) and jamf_docs_search by focusing on a single article via URL.

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?

The description specifies valid URL domains (docs.jamf.com or learn.jamf.com) and provides usage hints via parameters (e.g., summaryOnly for token efficiency, section for targeted extraction). It does not explicitly list when not to use this tool versus siblings, but the sibling names (batch, search, glossary, etc.) help the agent differentiate.

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