Skip to main content
Glama
Sign In
Apple Docs 2.0 MCP

Apple Docs 2.0 MCP

by mishafyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get WWDC Video

get_wwdc_video
Read-only

Retrieve a WWDC session's title, year, topics, video links, chapters, transcript with timestamps, code examples, and related sessions; set includeTranscript false to get only code or links.

Instructions

One WWDC session: its title, year and topics; its links, including the video downloads and the documentation it covers; its chapters; the full transcript, each paragraph with its time; every code example with the time it appears; and the sessions Apple lists as related. Transcripts are long: set includeTranscript to false when you need only the code or the links. view "related" lists the sessions related to it instead: those Apple lists, then, across every year, those that share the most of its topics.

Input Schema

NameRequiredDescriptionDefault
viewNo"session": the session itself. "related": the sessions related to it, first those Apple lists as related, then, across every year, sessions that share its topics, the most shared first; each with its year, link and topics, and whether it has a transcript and code.session
yearYesThe session's WWDC year ("2025").
limitNorelated: most sessions to show.
videoIdYesThe session's number, from its link: …/wwdc2025/10101/ is "10101".
includeCodeNosession: false leaves out the code examples.
includeTranscriptNosession: false leaves out the transcript, which runs to tens of KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / includeCode / description
      Previous value: -"Include all code examples from the session. Default: true"New value: +"session: false leaves out the code examples."
    • changedInput schema / properties / includeTranscript / description
      Previous value: -"Include the full transcript, as plain text without timestamps. Default: true"New value: +"session: false leaves out the transcript, which runs to tens of KB."
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 15,
+  "description": "related: most sessions to show.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "number"
+}
    • changedInput schema / properties / videoId / description
      Previous value: -"Session ID. Example: \"10101\" for keynote, \"238\" for session 238."New value: +"The session's number, from its link: …/wwdc2025/10101/ is \"10101\"."
    • addedInput schema / properties / view
      Added value: +{
+  "default": "session",
+  "description": "\"session\": the session itself. \"related\": the sessions related to it, first those Apple lists as related, then, across every year, sessions that share its topics, the most shared first; each with its year, link and topics, and whether it has a transcript and code.",
+  "enum": [
+    "session",
+    "related"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / year / description
      Previous value: -"WWDC year. Example: \"2025\""New value: +"The session's WWDC year (\"2025\")."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already establishes this as a safe read, so the bar is lower; the description still adds real value by warning that transcripts are long, with includeTranscript=false as the mitigation, and by noting what the 'related' view returns across all years. It says nothing about failure modes (bad year/videoId) or response size limits for the related list beyond the schema's limit.

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?

The payload enumeration is front-loaded and informative, but the final sentence re-explains the 'related' view mode almost verbatim from the schema, and the whole description is one sprawling colon-chained sentence that is harder to scan than it needs to be.

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

Completeness4/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 carries the burden of describing return contents, and it does so for both the session and related views, including the time-indexed transcript and code examples. It is complete enough to call correctly, though it omits error/empty-result behavior.

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 coverage is 100% and the schema descriptions already explain view, limit, includeCode and includeTranscript, including the tens-of-KB transcript warning. The description's parameter text largely restates those schema strings rather than adding new semantics, so the baseline 3 applies.

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 names the resource precisely (one WWDC session) and enumerates exactly what comes back: title, year, topics, links/downloads, chapters, timestamped transcript, timestamped code examples, and related sessions. It also covers the alternate 'related' mode, so an agent can distinguish it from search_wwdc_content or list_wwdc_videos 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?

It gives conditional guidance for the two modes and for the expensive option ('set includeTranscript to false when you need only the code or the links'), which is exactly when-not-to-use behavior. It does not, however, state when to reach for this tool over the sibling search/list tools, so routing across tools is left implicit.

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