Skip to main content
Glama

Visibility Genies

Edit an action

edit_action

Change a saved action's title, why it matters, steps, pages or due day. Only the fields you give change; the others stay as saved. Ask the user before changing their actions. The change is logged on the action as made by your agent, and refreshes never overwrite it. Uses no credits or provider calls.

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": {
      "projectId": "<projectId>",
      "id": "<id>"
    },
    "name": "edit_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
whyNoA new reason why it matters.
dueOnNoThe day it is due, YYYY-MM-DD, or null for no due day.
pagesNoThe pages it affects, at most 20. Replaces the saved list; an empty list clears it.
stepsNoThe steps in order, one per item. Replaces the saved steps.
titleNoA new short task title, such as 'Add a title to /pricing'.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description must carry the real burden and mostly does: it discloses partial-update semantics ('Only the fields you give change'), an audit trail ('logged on the action as made by your agent'), persistence of the edit against refreshes, and zero cost ('no credits or provider calls'). The only missing piece is what happens on validation failure or whether an edit can be reverted.

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?

Four short sentences, front-loaded with the operation and field list, followed by patch semantics, the consent rule, and the cost/audit note. No sentence is filler; each conveys a distinct operational fact.

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?

With an output schema present, return values need no explanation, and the annotations cover the safety profile. The description still adds the things structured fields cannot express: partial update behavior, required user consent, edit attribution, and absence of cost. Enough for an agent to call it 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 schema already documents id, projectId, and each field's constraints, making the baseline a 3. The description adds genuine meaning beyond that by stating the patch semantics — omitted fields retain their saved values — which is not expressed anywhere in the schema and directly affects how the agent constructs the call.

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 ('Change') plus the resource ('a saved action') and enumerates the mutable fields: title, why, steps, pages, due day. That is more precise than the title alone. However, the sibling set contains both update_action and edit_action, and the description never says how this differs from update_action, leaving a real disambiguation gap.

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?

It supplies one concrete precondition — 'Ask the user before changing their actions' — which tells the agent to obtain consent before invoking. It does not say when to prefer edit_action over update_action or create_action, nor when editing is inappropriate, so the guidance is partial rather than routing-level.

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