Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

refresh_url_document_route

Refresh the content of a URL document in the knowledge base by providing its document ID. Use this to update outdated URL document content.

Instructions

Refresh Url Document Content

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": {
      "documentation_id": "<documentation_id>"
    },
    "name": "refresh_url_document_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentation_idYesThe id of a document from the knowledge base. This is returned on document addition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, covering the safety profile. The description adds nothing beyond that – it doesn't explain that refreshing re-fetches remote URL content, whether prior content is replaced, or what side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a four-word fragment with no wasted words, but it is under-specified rather than genuinely concise – there is no sentence structure or front-loaded guidance for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent, non-read-only operation on a knowledge base document, with no output schema, the description omits what refresh means, what it affects, and any result expectations. The annotation set cannot compensate for this missing behavioral context.

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% for the single documentation_id parameter, and the description adds no additional semantics (e.g., what happens if the ID is stale or invalid). Baseline 3 applies when the schema already documents the parameter.

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

Purpose2/5

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

The description 'Refresh Url Document Content' essentially restates the tool name and title without stating a distinct verb-object relationship or scope. It doesn't distinguish this from siblings like update_document_route, update_file_document_route, or create_url_document_route.

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 indication of when to use this tool versus alternatives such as update_document_route or create_url_document_route, nor any precondition (e.g., that the source URL changed). No exclusions or context are given.

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