Skip to main content
Glama

Run a macro

execute_macro
Destructive

Run a macro. Runs a macro's actions on the conversations named, in the background, as the person making the request. The response does not wait for the actions to finish. Requires feature: macros.

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": {
      "macro_id": "<macro_id>",
      "conversation_ids": "<conversation_ids>"
    },
    "name": "execute_macro"
  }
}

Input Schema

NameRequiredDescriptionDefault
macro_idYesThe ID of the macro
conversation_idsYesThe conversation numbers (display IDs) to run the macro on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the description is not required to restate the safety profile. It adds genuinely non-obvious behavior: execution is asynchronous in the background, the response returns before the actions finish, actions are attributed to the requesting user, and the `macros` feature gate is required. None of this is derivable from the annotations or schema, and nothing contradicts them.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the core action, then the async behavior, then the feature requirement. Minor redundancy between the opening 'Run a macro' and the following 'Runs a macro's actions', but nothing extraneous.

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 two-parameter mutation with full schema coverage and no output schema, the definition covers what an agent most needs: it is asynchronous, acts as the calling user, and is feature-gated. Remaining gaps are modest — no statement about failure behavior (e.g. invalid macro or conversation IDs) or rate limits, and no note on how progress can be observed after the non-blocking response.

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%, with both macro_id and conversation_ids documented, so the baseline is 3. The description adds only that the macro acts on 'the conversations named', which restates the schema rather than clarifying formats, ordering, limits, or what happens with invalid conversation IDs. No extra meaning beyond the structured fields.

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?

The description gives a specific verb and resource plus scope: 'Runs a macro's actions on the conversations named.' That is clearly distinguishable from the CRUD siblings (create_macro, update_macro, delete_macro) because it executes rather than manages definitions. It stops short of naming any sibling explicitly, so it is clear but not sibling-routing.

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 by the mechanics: you need a macro and conversation IDs, and the `macros` feature must be enabled. There is no explicit when-to-use/when-not-to-use guidance, no note on preconditions such as whether the caller must own the macro, and no alternatives offered. Adequate but leaves the agent to infer the decision boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources