Skip to main content
Glama
Sign In
Apple Docs 2.0 MCP

Apple Docs 2.0 MCP

by mishafyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search WWDC Content

search_wwdc_content
Read-only

Search WWDC session transcripts and code to find sessions or code examples covering an API or technique, returning matches with passages, excerpts, and timestamps.

Instructions

Search what WWDC sessions said and showed, every year since 2014: the full text of their transcripts and their code. Returns the sessions whose transcript or code contains the query, most matches first, each with its count of matches and its first matching passages and code excerpts, with the time each comes up. Use it to find the sessions that cover an API or a technique; read one with get_wwdc_video. view "examples" lists the code itself instead: each example that contains query (pass the type or attribute the code uses, "LanguageModelSession", "@Generable"), with its session, year and time, newest year first. The answer also names a folder of every session as text, for a grep across sessions.

Input Schema

NameRequiredDescriptionDefault
viewNo"sessions": the matching sessions, most matches first, each with its count of matches and up to 3 passages or code excerpts, each with its time. "examples": the code examples that contain query, each with its session, year and the time it appears, newest year first.sessions
yearNoKeeps one WWDC year ("2025"); left out, every year.
limitNoMost sessions to show, 20 if left out; examples: most examples, 30.
queryYessessions: text a transcript paragraph or a line of code must contain, as typed, in any case ("@Observable", "Vision Pro"; "async await" finds the two words side by side). examples: text the code must contain, in any case: a type, attribute, method or framework name ("LanguageModelSession", "@Generable"); session code rarely shows its imports, so a framework's name finds fewer.
topicNoexamples: a topic ID, as list_wwdc_videos with view "topics" lists them, keeps that topic's sessions; any other text keeps the sessions whose title or topic names contain it, in any case.
searchInNosessions: search the transcripts, the code, or both.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • removedInput schema / properties / language
      Removed value: -{
-  "description": "Code language filter (\"swift\", \"objc\", \"javascript\"). Only for code search.",
-  "type": "string"
-}
    • removedInput schema / properties / limit / default
      Removed value: -20
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 20). Results include context snippets."New value: +"Most sessions to show, 20 if left out; examples: most examples, 30."
    • changedInput schema / properties / query / description
      Previous value: -"Search terms. Examples: \"async await\", \"@Observable\", \"Vision Pro\", \"performance optimization\"."New value: +"sessions: text a transcript paragraph or a line of code must contain, as typed, in any case (\"@Observable\", \"Vision Pro\"; \"async await\" finds the two words side by side). examples: text the code must contain, in any case: a type, attribute, method or framework name (\"LanguageModelSession\", \"@Generable\"); session code rarely shows its imports, so a framework's name finds fewer."
    • changedInput schema / properties / searchIn / description
      Previous value: -"Search scope. \"transcript\" = spoken content, \"code\" = code examples only, \"both\" = everything. Default: \"both\""New value: +"sessions: search the transcripts, the code, or both."
    • addedInput schema / properties / topic
      Added value: +{
+  "description": "examples: a topic ID, as list_wwdc_videos with view \"topics\" lists them, keeps that topic's sessions; any other text keeps the sessions whose title or topic names contain it, in any case.",
+  "type": "string"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "default": "sessions",
+  "description": "\"sessions\": the matching sessions, most matches first, each with its count of matches and up to 3 passages or code excerpts, each with its time. \"examples\": the code examples that contain query, each with its session, year and the time it appears, newest year first.",
+  "enum": [
+    "sessions",
+    "examples"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / year / description
      Previous value: -"Limit to specific year (\"2025\", \"2024\", etc.). Leave empty for all years."New value: +"Keeps one WWDC year (\"2025\"); left out, every year."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With only readOnlyHint available and no output schema, the description carries the return-shape burden and does so well: ordering ('most matches first', 'newest year first'), per-result contents (match count, first passages and code excerpts, timestamps), and an extra artifact (a folder of every session as text for grepping). This is behavioral context well beyond what the annotation declares.

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?

Front-loads the core purpose in the first clause and every sentence carries information about behavior or the two view modes. The dense, quote-heavy middle section is somewhat rambling and harder to parse than necessary, but there is no filler.

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 a six-parameter read-only search with no output schema, the description covers corpus scope, both view modes, ranking, result contents, and the sibling to use for follow-up reads. An agent has everything needed to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and each parameter is documented there, so the baseline is 3. The prose largely restates the schema (view modes, query semantics, type/attribute hints for examples), adding little net-new meaning beyond the structured field descriptions.

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 (search) and a precisely bounded resource (WWDC session transcripts and code, 2014 onward), and implicitly separates itself from get_wwdc_video and the apple-docs siblings. An agent knows exactly what corpus is being searched without opening the schema.

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?

Gives clear context ('Use it to find the sessions that cover an API or a technique') and routes to get_wwdc_video for reading a single session, plus explains when to prefer the 'examples' view over the default. It does not, however, distinguish this tool from search_apple_docs or say when not to use it, so it falls short of full when/when-not coverage.

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

Deploy Server

Other Tools