Search CoreWise's public community library of extractions (videos, podcasts, articles, and PDFs already analyzed by other users). Returns titles, snippets, and share URLs. Useful to check whether a video has already been extracted before starting a new extraction. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10, max 25). | |
| query | Yes | Search terms matched against titles and content. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the data scope (public community library), return contents (titles, snippets, share URLs), and that no API key is required. These are meaningful behavioral traits not implied by the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with the core purpose, then adds the use case and a final note on authentication. Every sentence earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with two parameters and no output schema, the description covers the essential context: what is searched, what is returned, the intended use case, and authentication. It is sufficiently complete for the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters are fully described in the schema (100% coverage), including default/max for limit and matching for query. The tool description adds no extra parameter semantics, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Search') and a specific resource ('CoreWise's public community library of extractions'), and distinguishes the tool from siblings by focusing on searching existing extractions rather than creating or retrieving single extractions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear use case: 'Useful to check whether a video has already been extracted before starting a new extraction.' This gives timely context and implies the alternative of starting a new extraction (i.e., using a sibling tool), though it doesn't explicitly name the alternative tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct function: extract_url initiates extraction, get_extraction retrieves structured results, get_transcript fetches raw source text, and search_public_extractions queries the public library. There is no overlap in purpose, and descriptions clearly differentiate them.
Tool names follow a consistent verb_noun pattern (extract_url, get_extraction, get_transcript, search_public_extractions), all using lowercase snake_case. The verbs vary but the structure is uniform, making it predictable.
Four tools precisely cover the server's scope: initiate, retrieve results, retrieve transcript, and search public content. This is an efficient size with no redundancy or missing essentials.
The tool set covers the full extraction lifecycle: create (extract_url), poll/read results (get_extraction), access raw data (get_transcript), and discover existing extractions (search_public_extractions). There are no obvious gaps for the stated purpose.