Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk

text_search_conversation_messages_route

Read-onlyIdempotent

Search across ElevenLabs conversation transcripts to find messages matching keywords. Filter results by agent, user, rating, language, topic, or call outcome.

Instructions

Text Search Conversation Messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoUsed for fetching next page. Cursor is returned in the response.
sort_byNoSort order for search results. 'search_score' sorts by search score, 'created_at' sorts by conversation start time.
user_idNoFilter conversations by the user ID who initiated them.
agent_idNoAgent id (agent_…) or speech engine external id (seng_), resolved to the same underlying resource.
branch_idNoFilter conversations by branch ID.
page_sizeNoNumber of results per page. Max 50.
text_onlyNo
topic_idsNoFilter conversations by topic IDs assigned during topic discovery.
rating_maxNoMaximum overall rating (1-5).
rating_minNoMinimum overall rating (1-5).
text_queryYesThe search query text for full-text and fuzzy matching
tool_namesNoFilter conversations by tool names used during the call.
version_idNoFilter conversations by version ID.
summary_modeNoWhether to include transcript summaries in the response.
main_languagesNoFilter conversations by detected main language (language code).
call_successfulNoThe result of the success evaluation
exclude_statusesNoExclude conversations with the given statuses. Useful for hiding in-progress / processing conversations from list views.
evaluation_paramsNoEvaluation filters. Repeat param. Format: criteria_id:result. Example: eval=value_framing:success
visited_agent_idsNoFilter conversations where any of these agents participated. Can not exceed 50 values.
tool_names_erroredNoFilter conversations by tool names that had errored calls.
termination_reasonsNoFilter conversations by their stored termination_reason (metadata.termination_reason). Repeat param to match any of several.
has_feedback_commentNoFilter conversations with user feedback comments.
call_start_after_unixNoUnix timestamp (in seconds) to filter conversations after to this start date.
tool_names_successfulNoFilter conversations by tool names that had successful calls.
call_duration_max_secsNoMaximum call duration in seconds.
call_duration_min_secsNoMinimum call duration in seconds.
call_start_before_unixNoUnix timestamp (in seconds) to filter conversations up to this start date.
data_collection_paramsNoData collection filters. Repeat param. Format: id:op:value where op is one of eq|gt|gte|lt|lte|missing.
dynamic_variable_paramsNoDynamic variable filters. Repeat param. Format: name:op:value where op is one of eq|gt|gte|lt|lte. Comparison operators require a numeric value. Names containing ':' cannot be expressed.
triggered_procedure_idsNoFilter conversations where any of these procedures were triggered. Can not exceed 50 values.
visited_agent_branch_idsNoFilter conversations where any of these agent branches participated. Can not exceed 50 values.
conversation_product_typeNoRestrict results to a single conversation product surface.
include_invalid_tool_callsNoAlso match tool calls that never ran.
conversation_initiation_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds no additional behavioral context such as pagination behavior, search semantics, required permissions, or result characteristics.

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

Conciseness2/5

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

The description is a single phrase, but it is under-specified rather than meaningfully concise. It repeats the title and provides no front-loaded operational information beyond the name.

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

Completeness1/5

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

For a 34-parameter conversation-message search tool with a closely related sibling and no output schema, this description is inadequate. It does not explain search scope, filtering behavior, pagination, or how to choose this tool over alternatives.

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 94%, so the schema already documents nearly all 34 parameters thoroughly. The description adds no extra parameter meaning, so the baseline of 3 is appropriate when the schema carries the burden.

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 is only "Text Search Conversation Messages", which essentially restates the tool name/title. It names the resource and search action but adds no explanatory detail and does not distinguish it from the sibling smart_search_conversation_messages_route.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to use it, or how it differs from alternatives such as smart_search_conversation_messages_route. The description gives no context for tool selection.

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