Skip to main content
Glama
Sign In

Aide

by app.aide
OverviewDiscussionsAdmin

List operations

list_operations
Read-only

List the Aide API operations (https://docs.aide.app/api-reference) in one area that this connection can run, each with its name, title, description, kind (read, create, update or delete) and inputSchema. Each kind runs with its own tool: run_read_operation, run_create_operation, run_update_operation or run_delete_operation.

Input Schema

NameRequiredDescriptionDefault
areaYesThe area: `topics` (Read, create, edit and delete topics, their categories, training examples and near misses; accept or dismiss suggested topics); `knowledge` (Move and delete articles; help center collections; business facts; product pairings; rename, narrow or delete knowledge sources; policy questions); `analytics` (Conversation counts, the support report (resolution, handoffs, response times, CSAT, sales), customer satisfaction with comments, and which knowledge answered); `agents` (Instructions agents follow in every conversation (list, add, edit, delete, reorder), handoff messages and reasons, Copilot drafting settings, and taking an inbox away from the AI agent); `channels` (A connection's details, inboxes and disconnecting it, reply settings and rollout, helpdesk extras (AI agent rule, sidebar, agent links, Salesforce sync, activity and retries), the support mailbox list, and the chat widget's settings); `helpdesk` (Inbox, CSAT and sender settings, routing and sender rules, SLA policies, schedules and holidays, custom fields and saved views); `scenarios` (Procedures: create, edit and delete them, save a draft and set it live, versions, check a When to use on recent conversations, Only if condition values, estimate and preview, run on existing conversations, list fields for collect steps; read, fill, create, edit and delete macros); `conversations` (Act on conversations: reply, notes, status, priority, assignee or team (also in bulk), take over or hand back, CSAT, macros, Copilot, draft feedback; order refunds, cancels, address, items, reships, returns and holds); `team` (Teammates, teams and invitations: roles, team membership, invite, resend or revoke, remove a teammate, transfer ownership); `billing` (The billing summary, plans, ending the trial, cancelling or keeping the subscription, the Stripe billing portal and AI usage).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"The area: `topics` (Read, create, edit and delete topics, their categories and training examples; accept or dismiss suggested topics); `knowledge` (Move and delete articles; help center collections; business facts; product pairings; rename, narrow or delete knowledge sources; policy questions); `analytics` (Conversation counts, the support report (resolution, handoffs, response times, CSAT, sales), customer satisfaction with comments, and which knowledge answered); `agents` (Instructions agents follow in every conversation (list, add, edit, delete, reorder), handoff messages and reasons, Copilot drafting settings, and taking an inbox away from the AI agent); `channels` (A connection's details, inboxes and disconnecting it, reply settings and rollout, helpdesk extras (AI agent rule, sidebar, agent links, Salesforce sync, activity and retries), the support mailbox list, and the chat widget's settings); `helpdesk` (Inbox, CSAT and sender settings, routing and sender rules, SLA policies, schedules and holidays, custom fields and saved views); `scenarios` (Procedures: create, edit and delete them, save a draft and set it live, versions, check a When to use on recent conversations, Only if condition values, estimate and preview, run on existing conversations, list fields for collect steps; read, fill, create, edit and delete macros); `conversations` (Act on conversations: reply, notes, status, priority, assignee or team (also in bulk), take over or hand back, CSAT, macros, Copilot, draft feedback; order refunds, cancels, address, items, reships, returns and holds); `team` (Teammates, teams and invitations: roles, team membership, invite, resend or revoke, remove a teammate, transfer ownership); `billing` (The billing summary, plans, ending the trial, cancelling or keeping the subscription, the Stripe billing portal and AI usage)."New value: +"The area: `topics` (Read, create, edit and delete topics, their categories, training examples and near misses; accept or dismiss suggested topics); `knowledge` (Move and delete articles; help center collections; business facts; product pairings; rename, narrow or delete knowledge sources; policy questions); `analytics` (Conversation counts, the support report (resolution, handoffs, response times, CSAT, sales), customer satisfaction with comments, and which knowledge answered); `agents` (Instructions agents follow in every conversation (list, add, edit, delete, reorder), handoff messages and reasons, Copilot drafting settings, and taking an inbox away from the AI agent); `channels` (A connection's details, inboxes and disconnecting it, reply settings and rollout, helpdesk extras (AI agent rule, sidebar, agent links, Salesforce sync, activity and retries), the support mailbox list, and the chat widget's settings); `helpdesk` (Inbox, CSAT and sender settings, routing and sender rules, SLA policies, schedules and holidays, custom fields and saved views); `scenarios` (Procedures: create, edit and delete them, save a draft and set it live, versions, check a When to use on recent conversations, Only if condition values, estimate and preview, run on existing conversations, list fields for collect steps; read, fill, create, edit and delete macros); `conversations` (Act on conversations: reply, notes, status, priority, assignee or team (also in bulk), take over or hand back, CSAT, macros, Copilot, draft feedback; order refunds, cancels, address, items, reships, returns and holds); `team` (Teammates, teams and invitations: roles, team membership, invite, resend or revoke, remove a teammate, transfer ownership); `billing` (The billing summary, plans, ending the trial, cancelling or keeping the subscription, the Stripe billing portal and AI usage)."
  2. Changed1 schema field changed
    • changedInput schema / properties / area / description
      Previous value: -"The area: `topics` (Read, create, edit and delete topics, their categories and training examples; accept or dismiss suggested topics); `knowledge` (Move and delete articles; help center collections; business facts; product pairings; rename, narrow or delete knowledge sources; policy questions); `analytics` (Conversation counts, the support report (resolution, handoffs, response times, CSAT, sales), customer satisfaction with comments, and which knowledge answered); `agents` (Handoff messages and reasons, Copilot drafting settings, and taking an inbox away from the AI agent); `channels` (A connection's details, inboxes and disconnecting it, reply settings and rollout, helpdesk extras (AI agent rule, sidebar, agent links, Salesforce sync, activity and retries), the support mailbox list, and the chat widget's settings); `helpdesk` (Inbox, CSAT and sender settings, routing and sender rules, SLA policies, schedules and holidays, custom fields and saved views); `scenarios` (Create, edit, delete, estimate and preview scenarios, their condition values, run them on existing conversations, list fields for COLLECT_FIELD; read, fill, create, edit and delete macros); `conversations` (Act on conversations: reply, notes, status, priority, assignee or team (also in bulk), take over or hand back, CSAT, macros, Copilot, draft feedback; order refunds, cancels, address, items, reships, returns and holds); `team` (Teammates, teams and invitations: roles, team membership, invite, resend or revoke, remove a teammate, transfer ownership); `billing` (The billing summary, plans, ending the trial, cancelling or keeping the subscription, the Stripe billing portal and AI usage)."New value: +"The area: `topics` (Read, create, edit and delete topics, their categories and training examples; accept or dismiss suggested topics); `knowledge` (Move and delete articles; help center collections; business facts; product pairings; rename, narrow or delete knowledge sources; policy questions); `analytics` (Conversation counts, the support report (resolution, handoffs, response times, CSAT, sales), customer satisfaction with comments, and which knowledge answered); `agents` (Instructions agents follow in every conversation (list, add, edit, delete, reorder), handoff messages and reasons, Copilot drafting settings, and taking an inbox away from the AI agent); `channels` (A connection's details, inboxes and disconnecting it, reply settings and rollout, helpdesk extras (AI agent rule, sidebar, agent links, Salesforce sync, activity and retries), the support mailbox list, and the chat widget's settings); `helpdesk` (Inbox, CSAT and sender settings, routing and sender rules, SLA policies, schedules and holidays, custom fields and saved views); `scenarios` (Procedures: create, edit and delete them, save a draft and set it live, versions, check a When to use on recent conversations, Only if condition values, estimate and preview, run on existing conversations, list fields for collect steps; read, fill, create, edit and delete macros); `conversations` (Act on conversations: reply, notes, status, priority, assignee or team (also in bulk), take over or hand back, CSAT, macros, Copilot, draft feedback; order refunds, cancels, address, items, reships, returns and holds); `team` (Teammates, teams and invitations: roles, team membership, invite, resend or revoke, remove a teammate, transfer ownership); `billing` (The billing summary, plans, ending the trial, cancelling or keeping the subscription, the Stripe billing portal and AI usage)."
  3. Added

TDQS

A4/5.0
Behavior3/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 meaningful context beyond that: results are filtered to what 'this connection can run' and each entry carries name, title, description, kind, and inputSchema, which tells the agent how to chain into a run_* tool. Return breadth and any truncation behavior remain undocumented, so it adds value but not rich depth.

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, front-loaded with the verb and resource, followed immediately by the return shape and the routing to the run_* tools. No filler, no restatement of the title.

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?

With no output schema, the description correctly compensates by enumerating the returned fields (name, title, description, kind, inputSchema) and explaining the permission scoping. Combined with a 100%-covered enum schema and full annotations, an agent has what it needs; only chaining specifics, such as passing the returned inputSchema into the matching run_* tool, are left implicit.

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% and the single enum parameter already spells out all ten areas in detail, so the schema carries the burden. The description only contributes the scoping phrase 'in one area that this connection can run', adding little per-parameter meaning beyond what is already structured.

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?

States a specific verb and resource ('List the Aide API operations'), the scope ('in one area that this connection can run'), and the exact shape of each item returned. It is clearly distinguishable from the domain list_* siblings (list_topics, list_procedures) because it enumerates API operations rather than domain objects.

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

Usage Guidelines4/5

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

The second sentence names the alternatives explicitly — run_read_operation, run_create_operation, run_update_operation, run_delete_operation — so an agent knows this tool discovers and those execute. It stops short of an explicit sequencing rule ('call this first, then run_* with the returned inputSchema') or a when-not-to-use statement, which keeps it from a 5.

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