Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Search Jamf Documentation

jamf_docs_search
Read-onlyIdempotent

Search Jamf product documentation by keywords and filter by product, topic, or version to find relevant articles with titles, snippets, and direct links.

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.13.0") or "current"

  • language (string, optional): Documentation language/locale (default: en-US)

  • 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 }, // Pages outside the product documentation, matched on title and ranked // separately from "results", which carry no score to rank them against. // Omitted when none matched. "otherSources"?: [{ "title": string, "url": string, "source": string }] }

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 option: expected one of ..." (an input validation error) if product, topic, docType or language is not one of the values the input schema lists

Note: Results are ranked by relevance. Use filters and pagination to navigate large result sets. Most results carry a mapId + contentId pair; pass both to jamf_docs_get_article to fetch that article directly instead of resolving its URL. The pair is omitted when a result comes from a source that does not resolve one — fall back to the URL in that case.

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, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener
versionNoFilter by version (e.g., "11.13.0") or "current"
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN
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
limitNo
queryYes
filtersNo
hasMoreYes
resultsYes
totalPagesYes
suggestionsNo
versionNoteNo
otherSourcesNo
totalResultsYes
relevanceNoteNo
paginationNoteNo
filterRelaxationNo
truncatedContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.0.12
    • addedOutput schema / properties / results / items / properties / crossFiled
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed8 schema fields changedv5.10.1
    • changedInput schema / properties / language / description
      Previous value: -"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH"New value: +"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN"
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "en-US",
      -  "ja-JP",
      -  "zh-TW",
      -  "de-DE",
      -  "es-ES",
      -  "fr-FR",
      -  "nl-NL",
      -  "th-TH"
      -]New value: +[
      +  "en-US",
      +  "ja-JP",
      +  "zh-TW",
      +  "de-DE",
      +  "es-ES",
      +  "fr-FR",
      +  "nl-NL",
      +  "th-TH",
      +  "it-IT",
      +  "pt-BR",
      +  "zh-CN"
      +]
    • changedInput schema / properties / product / description
      Previous value: -"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"New value: +"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener"
    • changedInput schema / properties / product / enum
      Previous value: -[
      -  "jamf-pro",
      -  "jamf-school",
      -  "jamf-connect",
      -  "jamf-protect",
      -  "jamf-now",
      -  "jamf-safe-internet",
      -  "jamf-insights",
      -  "jamf-rapididentity",
      -  "jamf-trust",
      -  "jamf-routines",
      -  "self-service-plus",
      -  "jamf-app-catalog"
      -]New value: +[
      +  "jamf-pro",
      +  "jamf-school",
      +  "jamf-connect",
      +  "jamf-protect",
      +  "jamf-now",
      +  "jamf-safe-internet",
      +  "jamf-insights",
      +  "jamf-rapididentity",
      +  "jamf-trust",
      +  "jamf-routines",
      +  "self-service-plus",
      +  "jamf-app-catalog",
      +  "jamf-account",
      +  "jamf-security-cloud",
      +  "elevate",
      +  "composer",
      +  "jamf-parent",
      +  "jamf-teacher",
      +  "jamf-setup-reset",
      +  "jamf-assessment",
      +  "title-editor",
      +  "jamf-infrastructure-manager",
      +  "jamf-adcs-connector",
      +  "jamf-pki-proxy",
      +  "jamf-migrate",
      +  "jamf-remote-assist",
      +  "jamf-cloud-distribution-service",
      +  "healthcare-listener"
      +]
    • changedInput schema / properties / version / description
      Previous value: -"Filter by version (e.g., \"11.5.0\", \"10.x\")"New value: +"Filter by version (e.g., \"11.13.0\") or \"current\""
    • addedInput schema / properties / version / pattern
      Added value: +"^(?:current|\\d+(?:\\.\\d+)*)$"
    • addedOutput schema / properties / otherSources
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "source": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "title",
      +      "url",
      +      "source"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / otherVersions
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed6 schema fields changedv4.0.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / product / description
      Previous value: -"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect"New value: +"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / filters
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "docType": {
      +      "type": "string"
      +    },
      +    "language": {
      +      "type": "string"
      +    },
      +    "product": {
      +      "type": "string"
      +    },
      +    "topic": {
      +      "type": "string"
      +    },
      +    "version": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / limit
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / paginationNote
      Added value: +{
      +  "type": "string"
      +}
  4. Addedv3.0.34
  5. Removedv3.0.30
  6. First observedv3.0.25

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real value: result ranking by relevance, defined error messages, token truncation info, and the mapId+contentId hand-off/fallback-to-URL behavior. It omits things like rate limits or caching, hence not a 5.

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?

Purpose is front-loaded and the example block is genuinely useful, but the full JSON/Markdown Returns section duplicates the existing output schema and inflates length. Several Args lines also echo schema descriptions verbatim, so not every sentence earns its place.

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?

For an 11-parameter search tool with a full output schema, the description covers errors, ranking, pagination, filtering guidance, and the cross-tool hand-off to jamf_docs_get_article. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by supplying common topic values and a query-to-filter mapping table that shows how the parameters interact, which materially aids invocation despite much of the Args block restating 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?

States a specific verb and resource ('Search Jamf documentation for articles matching your query') and scopes it ('across all Jamf product documentation including Jamf Pro, Jamf School...'). An agent can immediately separate this from siblings like jamf_docs_get_article or jamf_docs_list_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 concrete context and a rich example set mapping natural-language queries to recommended product/topic filters, and routes the agent to jamf_docs_list_products for ID discovery and jamf_docs_get_article for fetching hits. It stops short of stating when NOT to use it (e.g., vs. batch_get_articles or glossary_lookup), so it is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.