Skip to main content
Glama

Search Apple Developer Forums

apple_forum_search
Read-onlyIdempotent

Search Apple Developer Forums posts by keyword to find ranked discussions on SwiftUI, Swift, Combine, and related topics, with titles, URLs, and content snippets.

Instructions

Full-text search across Apple Developer Forums posts ingested from RSS feeds. Covers SwiftUI, Swift, Combine, and other recent developer discussions. Returns ranked posts with title, URL, and content snippet.

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": "apple_forum_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch query, e.g. 'SwiftUI list performance', 'NavigationStack', 'Combine publisher'.
formatNoResponse formatmarkdown
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
  2. First observedv0.2.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant context: the data provenance (RSS ingestion), the recency/coverage limitation, and the shape of results ('ranked posts with title, URL, and content snippet'). It says nothing about ranking mechanics, rate limits, or result freshness, which keeps it from 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.

Conciseness5/5

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

Three short sentences: what it searches, what it covers, what it returns. The core action and corpus are front-loaded, and no sentence is filler or restates the title.

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?

With no output schema, the description does compensate by naming the returned fields, which is helpful. But for a paginated search tool it omits how `limit`/`offset` interact, what ordering 'ranked' actually means, and how the markdown vs json `format` choice affects output — enough missing detail to leave the definition only minimally viable.

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 description coverage is only 50%: `query` and `format` are documented in the schema, while `limit` and `offset` carry no descriptions at all. The description mentions none of the four parameters, so pagination behavior and default page size receive no explanation in either place — a clear gap it should have filled.

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?

The description gives a specific verb and resource ('Full-text search across Apple Developer Forums posts') and scopes the corpus ('ingested from RSS feeds', 'SwiftUI, Swift, Combine'). It does not, however, differentiate itself from the very similar sibling `swift_forum_search` or from `apple_search_all`, which an agent would likely hesitate between.

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

Usage Guidelines3/5

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

Usage is only implied by scope words such as 'recent developer discussions' and 'ingested from RSS feeds', which hint that coverage is limited to recent forum content rather than complete historical archives. There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for broader or documentation-oriented searches.

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