Skip to main content
Glama
Emasoft

apple-docs

by Emasoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browse_wwdc_topics

Read-only

List all WWDC topic categories and their IDs to find the right topic filters before searching or listing session videos by year and topic.

Instructions

List all WWDC topic categories with their IDs. Essential first step before using list_wwdc_videos with topic filtering. Returns topic IDs like "swiftui-ui-frameworks" that can be used in other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoFilter topic videos by year. Only when browsing specific topic.
limitNoMax videos per topic (default: 20).
topicIdNoTopic ID to explore. Available IDs: "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". Leave empty to see all topics with video counts.
includeVideosNoList videos in the topic. Set false for topic structure only. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description adds value by specifying the output (IDs) and their reuse in other tools. No destructive behavior or contradictions.

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?

Two sentences directly convey purpose, usage, and output without waste. Front-loaded with key action and appropriate detail.

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?

No output schema exists, but the description sufficiently explains the return value (IDs and usage). Parameter meanings are fully covered in schema. Complete enough for an agent.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds context beyond schema by mentioning that leaving topicId empty shows all topics with video counts, and provides example IDs.

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 clearly states the tool lists WWDC topic categories with IDs. It distinguishes itself from siblings like 'list_wwdc_videos' by positioning as the essential first step for topic filtering.

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?

Explicitly says 'Essential first step before using list_wwdc_videos with topic filtering', providing clear context and instruction on when to use this tool.

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