Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Get Jamf Documentation Article

jamf_docs_get_article
Read-onlyIdempotent

Fetch the full content of any Jamf documentation article from docs.jamf.com or learn.jamf.com, with options to extract specific sections or summaries.

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
navigationNo
tokenCountNo
lastUpdatedNo
contentLocaleNo
versionStatusNo
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, but the description adds important behavioral context beyond that: it mentions 'Large articles are intelligently truncated with remaining sections listed,' lists possible errors (404, invalid URL, section not found), and clarifies that summaryOnly is a token-efficient preview. These details help the agent predict and handle edge cases without contradicting any 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 (Args, Returns, Examples, Errors, Note) and is front-loaded with the main purpose. While it is lengthy, every section serves a purpose, and the JSON return example is useful given the tool's complexity. It is slightly redundant with the schema (e.g., listing default values), but that redundancy is acceptable for discoverability.

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 the tool's complexity (10 parameters, output schema, sibling tools), the description is highly complete. It covers return formats, error handling, truncation behavior, and provides multiple usage examples. The existence of an output schema does not reduce the value of the description's own Returns section, which clarifies how each parameter affects the response.

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

Parameters3/5

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

The schema descriptions cover 100% of parameters, so baseline is 3. The description adds examples and explains token efficiency, but its Args list omits mapId, contentId, and language, and incorrectly labels url as 'required' when the schema has no required fields. This misleading detail undermines the added value, making it a net-neutral contribution beyond the schema.

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 the tool's purpose: 'Retrieve the full content of a specific Jamf documentation article.' It uses a specific verb (retrieve) and resource (article), and distinguishes itself from siblings like search, list_products, and get_toc by focusing on fetching a known article's content.

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 context on when to use the tool: 'Works with any article from docs.jamf.com or learn.jamf.com.' Includes examples (e.g., full article, specific section, maxTokens) and a note about using the section parameter for long articles. However, it does not explicitly mention alternative tools like search or list_products, so it stops short of giving exclusionary guidance.

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