Skip to main content
Glama
Sign In

Aide

by app.aide
OverviewDiscussionsAdmin

Find a conversation

find_conversation
Read-only

Find conversations by a helpdesk's own id (externalId), keywords (q) or filters, which combine. Each has its id, subject, status, priority, channel, requester, assignee, team, a preview and timestamps. Next page: metadata.nextCursor as cursor, same filters and sort.

Input Schema

NameRequiredDescriptionDefault
qNoMatches the subject, the requester's name or email, or an Aide or helpdesk id.
sortNo`newest` activity first by default.
teamNoTeam ids (list_members) or `none`.
viewNoAn inbox view: `needs_a_person`, `mine`, `unassigned`, `waiting`, `on_hold`, `closed`, `handled_by_aide`, `resolved_by_aide`, `handoffs`, `team:<team id>` or a saved view id.
topicNoTopic ids (list_topics), `any` or `none`.
cursorNoThe previous page's `metadata.nextCursor`.
statusNoAny of these statuses.
channelNoChannels such as `zendesk`, `front`, `gorgias`, `gmail` or `chat`.
perPageNoAt most 100.
assigneeNoTeammate ids (list_members), `me`, `aide` (Aide is answering), `none` or `mentioned` (a note mentions me).
priorityNoAny of these priorities.
scenarioNoIds of scenarios that ran on it.
externalIdNoA Zendesk ticket id, a Front `cnv_…` or another helpdesk id, exact match.
resolvedByNoResolved by Aide or by a teammate (`person`).
createdAfterNoCreated at or after this time.
handoffStateNoAny of these handoff states.
createdBeforeNoCreated before this time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Only conversations assigned to one of these: teammate ids (from list_members), `me`, `aide` (Aide is answering), `none` or `mentioned` (a note mentions me)."New value: +"Teammate ids (list_members), `me`, `aide` (Aide is answering), `none` or `mentioned` (a note mentions me)."
    • changedInput schema / properties / channel / description
      Previous value: -"Only conversations on these channels, such as `zendesk`, `front`, `gorgias`, `gmail` or `chat`."New value: +"Channels such as `zendesk`, `front`, `gorgias`, `gmail` or `chat`."
    • changedInput schema / properties / createdAfter / description
      Previous value: -"Only conversations created at or after this time (ISO 8601)."New value: +"Created at or after this time."
    • changedInput schema / properties / createdBefore / description
      Previous value: -"Only conversations created before this time (ISO 8601)."New value: +"Created before this time."
    • changedInput schema / properties / cursor / description
      Previous value: -"The previous page's `metadata.nextCursor`, to read the next page in the same sort and filters."New value: +"The previous page's `metadata.nextCursor`."
    • changedInput schema / properties / externalId / description
      Previous value: -"The helpdesk's id for the conversation (a Zendesk ticket id, a Front `cnv_…`), exact match."New value: +"A Zendesk ticket id, a Front `cnv_…` or another helpdesk id, exact match."
    • changedInput schema / properties / handoffState / description
      Previous value: -"Only conversations in one of these handoff states (`aide_handling`, `handoff_requested`, `person_handling`, `returned_to_aide`)."New value: +"Any of these handoff states."
    • changedInput schema / properties / perPage / description
      Previous value: -"Conversations per page (at most 100)."New value: +"At most 100."
    • changedInput schema / properties / priority / description
      Previous value: -"Only conversations with one of these priorities."New value: +"Any of these priorities."
    • changedInput schema / properties / q / description
      Previous value: -"Keywords: matches the subject, the requester's name or email, or a conversation's Aide or helpdesk id."New value: +"Matches the subject, the requester's name or email, or an Aide or helpdesk id."
    • changedInput schema / properties / resolvedBy / description
      Previous value: -"Only conversations resolved by Aide (`aide`) or by a teammate (`person`)."New value: +"Resolved by Aide or by a teammate (`person`)."
    • changedInput schema / properties / scenario / description
      Previous value: -"Only conversations one of these scenarios (scenario ids) ran on."New value: +"Ids of scenarios that ran on it."
    • changedInput schema / properties / sort / description
      Previous value: -"The order: `newest` (latest activity, the default), `oldest`, `waiting_longest`, `priority` or `sla_due`."New value: +"`newest` activity first by default."
    • changedInput schema / properties / status / description
      Previous value: -"Only conversations with one of these statuses."New value: +"Any of these statuses."
    • changedInput schema / properties / team / description
      Previous value: -"Only conversations of one of these teams (team ids from list_members), or `none`."New value: +"Team ids (list_members) or `none`."
    • changedInput schema / properties / topic / description
      Previous value: -"Only conversations with one of these topics (ids from list_topics), or `any` / `none`."New value: +"Topic ids (list_topics), `any` or `none`."
    • changedInput schema / properties / view / description
      Previous value: -"Only conversations in this inbox view: `needs_a_person`, `mine`, `unassigned`, `waiting`, `on_hold`, `closed`, `handled_by_aide`, `resolved_by_aide`, `handoffs`, `team:<team id>` or a saved view id."New value: +"An inbox view: `needs_a_person`, `mine`, `unassigned`, `waiting`, `on_hold`, `closed`, `handled_by_aide`, `resolved_by_aide`, `handoffs`, `team:<team id>` or a saved view id."
  2. Changed3 schema fields changed
    • addedInput schema / properties / handoffState / items / type
      Added value: +"string"
    • addedInput schema / properties / priority / items / type
      Added value: +"string"
    • addedInput schema / properties / status / items / type
      Added value: +"string"
  3. Changed2 schema fields changed
    • addedInput schema / properties / resolvedBy / type
      Added value: +"string"
    • addedInput schema / properties / sort / type
      Added value: +"string"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the result shape (id, subject, status, priority, channel, requester, assignee, team, preview, timestamps) and the pagination contract, useful for a tool with no output schema.

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?

Two sentences, no filler: the targeting modes come first, then result contents, then pagination. Every clause carries information an agent needs.

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?

For a 17-parameter, no-output-schema tool it covers purpose, return fields and pagination adequately. Minor gaps remain: default behavior with no filters, and default sort/perPage are left to the schema.

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, but the description adds genuine meaning by stating that externalId, q and filters combine (conjunctive semantics not expressed in the schema) and by explaining that the next page reuses 'same filters and sort'.

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

Purpose4/5

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

States a specific verb and resource plus the three ways to target a conversation (externalId, q, filters) and enumerates the returned fields. It does not explicitly distinguish itself from the sibling get_conversation or search, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'filters, which combine' tells the agent this is the list/filter entry point, but there is no explicit when-to-use-this-vs-get_conversation or vs search, and no warning about unfiltered calls returning a broad result set.

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

All Aide 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