Skip to main content
Glama
Sign In

SavedThat

by app.savedthat
OverviewDiscussionsAdmin

Show creator libraries

show_creators
Read-onlyIdempotent

List the creators whose videos SavedThat has already transcribed (for example Alex Hormozi, Andrew Huberman, Y Combinator), with niche, video count, hours and sample questions, rendered as an interactive picker. Optional filters by name or niche. Use it when the user wants to learn from or work with a specific creator, or asks which creators are available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoOptional niche filter.
queryNoOptional part of a creator's name or handle.

Output Schema

NameRequiredDescriptionDefault
creatorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-derivable behavior: the result set is limited to creators already transcribed and is 'rendered as an interactive picker' with niche, video count, hours and sample questions. It does not disclose ordering or whether the full catalog is always returned.

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?

Three sentences, front-loaded with the resource and data scope, then filters, then usage. The parenthetical creator examples are illustrative rather than essential but are short and help ground the resource. No redundant or filler wording.

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 an output schema present and rich annotations, the description only needs to cover purpose, scope and triggers, all of which are addressed, including the important constraint that only pre-transcribed creators appear. Minor gaps remain around result set size, ordering, and empty-filter 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 description coverage is 100%, with both optional filters (niche enum, name/handle query) already documented in-schema. The description restates 'Optional filters by name or niche' without adding syntax, matching rules, or behavior when filters match nothing, so it adds little beyond the structured data. 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 the creators'), scopes the data to what SavedThat has 'already transcribed', and gives concrete examples (Hormozi, Huberman, Y Combinator) plus the fields returned. An agent can distinguish this catalog-browsing tool from search_creator_videos or list_my_saves 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 Guidelines4/5

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

Explicitly names the triggering conditions: the user wants to learn from or work with a specific creator, or asks which creators are available. It stops short of naming a when-not or a specific sibling to use instead (e.g. search_creator_videos for finding videos rather than creators), so routing is clear but not fully disambiguated.

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

All SavedThat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources