Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

search_message_ids

Read-only

Find message IDs by notification status, mentions, labels, creator, conversation, or workspace. Use when list_messages lacks these filters, then hydrate with get_message.

Instructions

Find message IDs by notified state, mentions, labels, creator, conversation or workspace — returning IDs plus cursor metadata. USE WHEN: Any filter list_messages cannot express: whether you were notified (notified_status), whether you were tagged (tagged_user_ids), or by label_ids. Cheap in tokens because it returns IDs only — hydrate the ones you need with get_message. USE INSTEAD: list_messages when a date range, conversation or workspace filter is all you need and you want full message bodies in one call. search_messages_by_heard_status for unread/listened state, which this tool cannot filter on. EXAMPLE: {"notified_status":"notified","limit":50} RETURNS: {ids: [{...}], has_more, next_cursor?}. Keep paging while has_more is true, passing next_cursor back as next_cursor. ERROR BAD_REQUEST: An ID list contains names rather than IDs, or exceeds 50 entries. — Resolve people to IDs with search_users and conversations with list_conversations; split lists longer than 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of message IDs to return (max 100).
has_notesNoFilter by whether the message has notes attached.both
label_idsNoOnly messages carrying these labels. Max 50 entries. Requires IDs, not names.
creator_idsNoOnly messages created by these users. Max 50 entries. Requires IDs, not names.
next_cursorNoPass the `next_cursor` from a previous response to fetch the next page.
workspace_idsNoOnly messages in these workspaces. Max 50 entries. Requires IDs, not names.
sort_directionNoDirection to walk from the anchor.newer
notified_statusNoFilter by whether you were notified about the message. `notified` = messages you were notified about, `not_notified` = the rest, `both` = no filter.both
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.
tagged_user_idsNoOnly messages where these users were tagged/mentioned. Max 50 entries. Requires IDs, not names.
conversation_idsNoOnly messages in these conversations. Max 50 entries. Requires IDs, not names.
created_or_updated_atNoISO 8601 timestamp anchor; a UTC `Z` suffix or a numeric offset both work. Combined with `sort_direction` to page backwards or forwards from a point in time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive behavior. The description adds meaningful behavioral detail: it returns IDs only and is token-cheap, pagination follows has_more/next_cursor, and BAD_REQUEST causes are explained with remediation steps. This goes well beyond what the annotations convey.

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

Conciseness5/5

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

The description is well-structured with clear sections: purpose, USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, and ERROR. It is front-loaded with a one-sentence purpose statement, and every section earns its place by carrying actionable guidance.

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

Completeness5/5

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

Even without an output schema, the description provides the return envelope and pagination contract, error handling guidance, and explicit sibling alternatives. Combined with fully documented schema parameters and read-only annotations, an agent has everything it needs to select and invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining which parameter groups matter (notified, tagged, label filters), how next_cursor works for paging, and that ID lists require IDs rather than names with a 50-entry limit. Most parameter-level detail still lives in the schema, but the description supplements it usefully.

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?

The description opens with a specific verb and resource: 'Find message IDs by notified state, mentions, labels, creator, conversation or workspace — returning IDs plus cursor metadata.' It immediately differentiates the tool from siblings like list_messages and search_messages_by_heard_status, so an agent can understand what this tool uniquely does.

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

Usage Guidelines5/5

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

The USE WHEN and USE INSTEAD sections give explicit routing guidance: use this for filters list_messages cannot express (notified_status, tagged_user_ids, label_ids), and use list_messages when full bodies are needed, or search_messages_by_heard_status for heard state. This leaves little ambiguity about when to select this tool over alternatives.

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