Skip to main content
Glama

Search App Store Review Guidelines

appstore_guidelines_search
Read-onlyIdempotent

Search App Store Review Guidelines by keyword to retrieve matching section titles, excerpts, and source references for compliance checks.

Instructions

Search indexed App Store Review Guidelines sections by keyword and return matching section titles, excerpts, and source references.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "appstore_guidelines_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch query, e.g. 'privacy tracking', 'in-app purchase', 'advertising', 'kids category'.
formatNoResponse formatmarkdown
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / query / maxLength
      Added value: +500
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. First observedv0.2.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful return-shape context (titles, excerpts, source references) that no output schema provides, but says nothing about pagination behavior, result ranking, or whether excerpts are truncated — gaps that matter for a search tool with limit/offset.

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?

A single front-loaded sentence with a clear verb-resource-object structure and no filler. Its brevity is close to the edge of under-specification, but every word present earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core search semantics and the shape of returned data, which is the most important thing given there is no output schema. For a four-parameter tool with 50% schema coverage and a closely related get-sibling, it should also address pagination limits and when to use it versus fetching a specific guideline.

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

Parameters2/5

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

Schema coverage is 50%: query and format are documented in the schema, while limit and offset carry no descriptions. The description adds no compensating detail — "by keyword" merely restates the query parameter, and it never mentions result capping, pagination, or the markdown/json output switch.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Search") and a specific resource ("indexed App Store Review Guidelines sections"), plus what the results contain. It does not, however, distinguish itself from the sibling appstore_guideline_get, which presumably fetches a known section — the agent must infer the search-vs-fetch split from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no mention of when to prefer this over appstore_guideline_get (once you know a section) or over the cross-cutting apple_search_all. The keyword-based nature implies exploratory lookup, but nothing explicit tells the agent when this tool is the right choice.

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