Skip to main content
Glama

Get Reading Trail

get_reading_trail
Read-onlyIdempotent

Get an episode reading trail with citations and cursor pagination.

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": {
      "slug": "<slug>"
    },
    "name": "get_reading_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
operationYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / meta / properties / clip_catalog
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalog_id": {
      +      "const": "htrtf-youtube-clips",
      +      "type": "string"
      +    },
      +    "catalog_sha256": {
      +      "pattern": "^[a-f0-9]{64}$",
      +      "type": "string"
      +    },
      +    "catalog_version": {
      +      "maxLength": 80,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "generated_at": {
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "catalog_id",
      +    "catalog_version",
      +    "catalog_sha256",
      +    "generated_at"
      +  ],
      +  "type": "object"
      +}
  2. Changed31 schema fields changed
    • addedOutput schema / properties / data / properties / items / items / properties / evidence / items / properties / end_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / items / items / properties / evidence / items / properties / start_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / total / maximum
      Added value: +9007199254740991
    • removedOutput schema / properties / meta / properties / artifact_manifest_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / artifact_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / release_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / release_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / release_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / rights / properties / policy_url / $ref
      Removed value: -"#/properties/meta/properties/canonical_url"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / format
      Added value: +"uri"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / maxLength
      Added value: +2048
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / snapshot_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / content_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / transcript_version / type
      Added value: +"string"
  3. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that results include citations and use cursor pagination, which is genuine extra behavioral context. It still omits ordering, what a trail entry contains, and end-of-trail signaling, so it does not fully exploit the lower bar set by the annotations.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity borders on under-specification rather than pure conciseness.

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?

The presence of an output schema means return values need not be documented, and annotations cover the mutation semantics, so what remains missing is guidance-level rather than correctness-level. Still, with zero schema description coverage, the description leaves an agent guessing about 'limit' and about when this tool beats its siblings.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the burden and largely does not. It explains the 'cursor' parameter indirectly via 'cursor pagination' and implies 'slug' identifies the episode, but 'limit' (default 15, max 25) is never mentioned and no format expectations are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Get') and a resource ('episode reading trail'), which distinguishes it from get_episode or get_clip by resource name. However, 'reading trail' is undefined jargon, so an agent cannot tell what content actually comes back without opening the schema or output schema. Purpose is identifiable but not fully clear.

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 statement of when to use this tool versus get_episode, get_transcript_segment, or get_flashcards, and no prerequisites or exclusions. The agent must infer selection from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources