Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Search Jamf Documentation

jamf_docs_search
Read-onlyIdempotent

Search Jamf documentation for articles on Jamf Pro, School, Connect, Protect, and more. Filter results by product, topic, version, and document type to find relevant guides.

Instructions

Search Jamf documentation for articles matching your query.

This tool searches across all Jamf product documentation including Jamf Pro, Jamf School, Jamf Connect, Jamf Protect, Jamf Now, Jamf Safe Internet, and more. Results include article titles, snippets, and direct links.

Args:

  • query (string, required): Search keywords (2-200 characters)

  • product (string, optional): Filter by product ID (use jamf_docs_list_products to see all)

  • topic (string, optional): Filter by topic. Common: enrollment, profiles, policies, packages, scripts, patch, apps, security, filevault, sso, identity-provider, inventory, reports, api, network. See jamf_docs_list_products for the full list of 40 topic IDs.

  • docType (string, optional): Filter by document type: documentation, release-notes, training, solution-guide, glossary, getting-started

  • version (string, optional): Filter by version (e.g., "11.5.0", "10.x")

  • limit (number, optional): Maximum results per page 1-50 (default: 10)

  • page (number, optional): Page number for pagination 1-100 (default: 1)

  • maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000)

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

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

Returns: For JSON format: { "total": number, "query": string, "results": [...], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "pagination": { "page": number, "pageSize": number, "totalPages": number, "totalItems": number, "hasNext": boolean, "hasPrev": boolean } }

For Markdown format: A formatted list of search results with pagination and token info.

Examples (common query → recommended filters):

  • "Configure SSO with Okta in Jamf Connect" → query="SSO Okta", product="jamf-connect", topic="sso"

  • "Set up FileVault encryption" → query="FileVault encryption", product="jamf-pro", topic="filevault"

  • "Patch macOS apps" → query="patch policy", product="jamf-pro", topic="patch"

  • "Smart group criteria" → query="smart group criteria", product="jamf-pro", topic="reports"

  • "Automated Device Enrollment workflow" → query="ADE prestage", product="jamf-pro", topic="enrollment"

  • "Shared iPad in a classroom" → query="shared iPad classroom", product="jamf-school", topic="education"

  • "Jamf Protect custom analytic" → query="custom analytic", product="jamf-protect", topic="protect-analytics"

  • "Jamf Pro REST API authentication" → query="API role bearer token", product="jamf-pro", topic="api"

  • "Extension attribute scripts" → query="extension attribute script", product="jamf-pro", topic="extension-attributes"

  • "Paginate through results" → query="policy", page=2

Errors:

  • "No results found" if search returns empty

  • "Invalid product ID" if product parameter is not recognized

Note: Results are ranked by relevance. Use filters and pagination to navigate large result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keywords to find in Jamf documentation
productNoFilter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect
topicNoFilter by topic. Common: enrollment, profiles, policies, packages, scripts, patch, apps, security, filevault, sso, identity-provider, inventory, reports, api, network. See jamf_docs_list_products for the full list of 40 topic IDs.
versionNoFilter by version (e.g., "11.5.0", "10.x")
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH
docTypeNoFilter by document type: documentation, release-notes, training, solution-guide, glossary, getting-started
limitNoMaximum number of results per page (1-50)
pageNoPage number for pagination (1-100, default: 1)
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
queryYes
totalResultsYes
pageYes
totalPagesYes
hasMoreYes
resultsYes
suggestionsNo
filterRelaxationNo
versionNoteNo
relevanceNoteNo
truncatedContentNo
Behavior5/5

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

Discloses pagination, token limits, output formats, error messages, and ranking by relevance. Does not contradict annotations (readOnlyHint=true, destructiveHint=false) and adds context about result truncation and token info.

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?

Well-structured with clear sections (Args, Returns, Examples, Errors, Note), but somewhat long due to exhaustive examples. Every sentence adds value; no redundancy with schema.

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?

Covers all aspects: purpose, parameters, output, errors, examples, and cross-references sibling tools (jamf_docs_list_products). Annotations and output schema reduce the description's burden, and it still provides comprehensive guidance.

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%, and the description adds value beyond schema by providing example queries, common topic values, and default parameter values. The explanation of outputMode and responseFormat clarifies usage.

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 it searches Jamf documentation across multiple products. It lists result contents (titles, snippets, links) and distinguishes from siblings like jamf_docs_get_article (single article retrieval) and jamf_docs_list_products (listing products).

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 detailed query examples with recommended filters (product, topic) and references jamf_docs_list_products for product/topic IDs. However, it does not explicitly state when to use alternative tools like jamf_docs_get_article or jamf_docs_batch_get_articles.

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