Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Search Jamf Documentation

jamf_docs_search
Read-onlyIdempotent

Search all Jamf product documentation to find articles with titles, snippets, and direct links. Filter results by product, topic, or document type for precise answers.

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
pageNoPage number for pagination (1-100, default: 1)
limitNoMaximum number of results per page (1-50)
queryYesSearch keywords to find in Jamf documentation
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.
docTypeNoFilter by document type: documentation, release-notes, training, solution-guide, glossary, getting-started
productNoFilter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect
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
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
pageYes
queryYes
hasMoreYes
resultsYes
totalPagesYes
suggestionsNo
versionNoteNo
totalResultsYes
relevanceNoteNo
filterRelaxationNo
truncatedContentNo
Behavior4/5

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

Annotations confirm read-only, idempotent, non-destructive behavior. The description adds behavioral details like 'Results are ranked by relevance,' pagination behavior, and error messages. 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, and Errors. However, it is somewhat lengthy and could be slightly more concise.

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 high parameter count, full schema coverage, and presence of output schema, the description is thorough. It covers return format, pagination, token usage, and error scenarios.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by explaining parameter usage with examples, common values for topic and docType, and guidance on output modes and response formats.

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 'Search Jamf documentation for articles matching your query.' It distinguishes from siblings like jamf_docs_get_article by emphasizing search across multiple products and providing filtering options.

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 extensive usage guidance through examples, recommended filters, and notes on pagination. It mentions using jamf_docs_list_products for product IDs but does not explicitly state when not to use this tool.

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