Skip to main content
Glama
Sign In
Apple Docs 2.0 MCP

Apple Docs 2.0 MCP

by mishafyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List WWDC Videos

list_wwdc_videos
Read-only

Browse WWDC sessions from 2014 onward by year, topic, or title text, each with links, topics, and transcript or code availability. Use it to find which Apple developer talks to read next.

Instructions

List WWDC sessions, every year since 2014, by year, topic or text in the title or topic names: each with its title, link, topics, and whether it has a transcript and code, newest year first. Use it to browse sessions; search_wwdc_content finds what sessions said or showed, and get_wwdc_video reads one. view "years" counts each year's sessions; view "topics" lists the WWDC topics with their IDs and session counts, or one topic's sessions.

Input Schema

NameRequiredDescriptionDefault
viewNo"sessions": the sessions by year, topic or text in the title or topic names. "years": each WWDC year with its number of sessions, then how many sessions in all have code and a transcript. "topics": the WWDC topics with their IDs and session counts or, with topic, one topic's sessions, newest year first.sessions
yearNosessions, and one topic's sessions: keeps one WWDC year ("2026"); left out or "all", every year.
limitNoMost sessions to show: 50 if left out, 20 of one topic's.
topicNosessions: 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. topics: one topic's ID, to list its sessions.
hasCodeNosessions: true keeps the sessions with code; false, those without.
includeVideosNotopics: false shows the topic without its sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • changedInput schema / properties / hasCode / description
      Previous value: -"Filter by code availability. true = sessions with code, false = without code. Leave empty for all."New value: +"sessions: true keeps the sessions with code; false, those without."
    • addedInput schema / properties / includeVideos
      Added value: +{
+  "default": true,
+  "description": "topics: false shows the topic without its sessions.",
+  "type": "boolean"
+}
    • removedInput schema / properties / limit / default
      Removed value: -50
    • changedInput schema / properties / limit / description
      Previous value: -"Max videos to show (default: 50). Videos include title, duration, and content indicators."New value: +"Most sessions to show: 50 if left out, 20 of one topic's."
    • changedInput schema / properties / topic / description
      Previous value: -"A topic ID keeps that topic's sessions: \"accessibility-inclusion\", \"app-services\", \"app-store-distribution-marketing\", \"audio-video\", \"business-education\", \"design\", \"developer-tools\", \"essentials\", \"graphics-games\", \"health-fitness\", \"machine-learning-ai\", \"maps-location\", \"photos-camera\", \"privacy-security\", \"safari-web\", \"spatial-computing\", \"swift\", \"swiftui-ui-frameworks\", \"system-services\". Any other text keeps the sessions whose title or topic names contain it."New value: +"sessions: 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. topics: one topic's ID, to list its sessions."
    • addedInput schema / properties / view
      Added value: +{
+  "default": "sessions",
+  "description": "\"sessions\": the sessions by year, topic or text in the title or topic names. \"years\": each WWDC year with its number of sessions, then how many sessions in all have code and a transcript. \"topics\": the WWDC topics with their IDs and session counts or, with topic, one topic's sessions, newest year first.",
+  "enum": [
+    "sessions",
+    "years",
+    "topics"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / year / description
      Previous value: -"WWDC year (\"2025\", \"2024\", etc.) or \"all\"; list_wwdc_years lists the years held. Example: \"2025\" for latest."New value: +"sessions, and one topic's sessions: keeps one WWDC year (\"2026\"); left out or \"all\", every year."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest, and it does: it discloses the returned fields per session (title, link, topics, transcript/code flags) and the sort order ("newest year first"). It also explains what each view mode counts or returns. It does not mention pagination behavior or the 200-item cap beyond what the schema states, so it stops short of 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.

Conciseness4/5

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

Front-loaded with the core operation and return shape, then routing guidance, then view-mode detail — a sensible order. It is dense but each sentence does work; the trailing view sentence overlaps noticeably with the schema's own view description, which is minor redundancy rather than waste.

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 six optional parameters, no required params, and no output schema, the description covers the essentials: what is listed, what fields come back, the ordering, the filter axes, and how it differs from siblings. The three view modes are all touched on. Only pagination/truncation behavior around the limit cap is left implicit, which keeps it just short of complete.

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%, so every parameter is already documented; the description's restatement of "years" and "topics" views largely duplicates the schema's view description. It adds the framing that these are alternative browse modes rather than filters, but contributes no syntax, default, or constraint detail beyond the schema. 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?

States a specific verb and resource ("List WWDC sessions") plus scope ("every year since 2014") and the facets it filters by (year, topic, title/topic text). It explicitly names the two nearest siblings — search_wwdc_content and get_wwdc_video — and what each does instead, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ("Use it to browse sessions") and contrasts it against both alternatives with their distinguishing behavior: search_wwdc_content "finds what sessions said or showed" and get_wwdc_video "reads one." The view-mode semantics ("years" counts, "topics" lists topics with IDs) further tell the agent which variant to pick.

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