Skip to main content
Glama

Create a deep link into a session

wwdc_session_deep_link
Read-onlyIdempotent

Create a WWDC session video deep link with a time query using seconds or a timestamp, so viewers open directly at the relevant chapter.

Instructions

Returns a URL with a ?time=SECONDS query so the user jumps straight to a chapter.

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": {
      "id": "<id>"
    },
    "name": "wwdc_session_deep_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
formatNoResponse formatmarkdown
secondsNo
timestampNoHH:MM:SS or MM:SS — alternative to seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / seconds / maximum
      Added value: +9007199254740991
  2. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the return shape (a URL containing a ?time=SECONDS query), which is the main behavioral fact an agent needs since there is no output schema. It does not cover behavior around conflicting time inputs or what the format parameter changes.

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?

One sentence, front-loaded with the concrete output and free of filler. The trailing purpose clause earns its place by motivating the tool, though nothing addresses the input trade-offs an agent must resolve.

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 correctly carries the return-value burden and does so briefly. However, for a 4-parameter tool at 50% schema coverage, it leaves open which time input wins, what id refers to (a session id), and what the format enum changes, so it is adequate rather than 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 coverage is 50%, so the schema documents format and timestamp while id and seconds are bare. The description usefully explains that seconds maps into the ?time= query, adding meaning beyond the bare integer, but it is silent on the timestamp alternative (HH:MM:SS or MM:SS) and on precedence when both are supplied, and it says nothing about how format=json vs markdown affects the response.

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 states a specific verb and output ("Returns a URL with a ?time=SECONDS query") plus the intent (jump straight to a chapter), which is meaningfully distinct from siblings like wwdc_get_session or wwdc_session_summary. It never names a sibling or explicitly contrasts itself, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many wwdc_* siblings. The clause "so the user jumps straight to a chapter" only implies the use case (handing a user a jump-to-moment link) rather than instructing the agent.

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