Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Batch Get Jamf Documentation Articles

jamf_docs_batch_get_articles
Read-onlyIdempotent

Fetch up to 10 Jamf documentation articles in a single request with parallel processing. Use for comparing articles or bulk research across multiple pages.

Instructions

Retrieve multiple Jamf documentation articles in a single request.

Fetches up to 10 articles in parallel with concurrency control. Useful for comparing articles, gathering information from multiple pages, or bulk research.

Args:

  • urls (string[], required): Array of 1-10 article URLs (must be from docs.jamf.com or learn.jamf.com)

  • concurrency (number, optional): Max parallel requests 1-5 (default: 3)

  • maxTokens (number, optional): Total token budget across all articles (default: 5000). Distributed evenly.

  • outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for brief output.

  • responseFormat ('markdown' | 'json'): Output format (default: 'markdown')

Returns: An array of article results. Each article independently succeeds or fails. For JSON format, returns a BatchResponse object with results, summary, and tokenInfo.

Examples:

  • Compare two products: urls=["https://learn.jamf.com/.../page/A.html", "https://learn.jamf.com/.../page/B.html"]

  • Bulk fetch with compact output: urls=[...], outputMode="compact", maxTokens=10000

Note: Token budget is split evenly across articles. Use higher maxTokens for more articles. Partial failures are reported per-article without failing the entire batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of Jamf documentation article URLs (1-10)
concurrencyNoMaximum parallel requests (1-5, default: 3)
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH
maxTokensNoTotal token budget across all articles (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
resultsYes
summaryYes
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral details: concurrency control, token budget distribution across articles, and partial failures. This goes beyond annotations without contradicting them.

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

Conciseness3/5

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

The description is structured with sections (Args, Returns, Examples, Note) and is informative, but somewhat verbose. It could be more concise while retaining clarity; for instance, combining some lines.

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 has 6 parameters and an output schema, the description covers all aspects: parameter semantics with examples, return behavior including failure handling, and limitations (max 10 articles, concurrency limits). It is comprehensive for the tool's complexity.

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 coverage is 100% with parameter descriptions. The description reiterates these and adds examples (e.g., comparing two products), explains token distribution, and defines output modes. It adds value beyond the schema by clarifying usage patterns.

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 verb 'Retrieve multiple Jamf documentation articles in a single request', specifying both the action and the resource. It differentiates from sibling tools like jamf_docs_get_article and jamf_docs_get_toc by emphasizing batch retrieval.

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 provides context for when to use this tool: 'useful for comparing articles, gathering information from multiple pages, or bulk research'. It implicitly contrasts with single-article retrieval, but does not explicitly list when not to use it or alternative tools.

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