Skip to main content
Glama

Visibility Genies

Update an action

update_action

Change a saved action's status, priority or assignee in this project. Set assigneeUserId to null to unassign, or use a current organization member id returned by list_actions. Marking done stamps its completion time; leaving done clears it. Dismissed audit findings return only above their dismissal baseline; other sources stay dismissed until manually restored. 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": "update_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusNo
priorityNo
projectIdYes
assigneeUserIdNo

Output Schema

NameRequiredDescriptionDefault
metaNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses real behavioral traits: no credits or provider calls consumed, completion time is stamped on 'done' and cleared when leaving it, and dismissed audit findings only re-surface above their baseline. That is meaningful context a caller could not infer from the schema. It stops short of saying what is returned or whether permission restrictions apply.

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?

Four tight sentences with the core mutation stated first and the special-case rules after it; no filler. The dismissal-baseline sentence is the most expensive and is only loosely related to a field-update call, keeping it just under a 5.

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 five-parameter mutation with an output schema, the description covers the important surprises: side-effecting status transitions, unassignment, and zero credit cost. Missing are permission/precondition requirements and confirmation that unspecified fields are left untouched.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does explain assigneeUserId's null-vs-member-id semantics and the side effect of status='done'. However, it says nothing about priority's enum levels or the non-done status values, and projectId is not clarified — leaving roughly half the parameter surface to inference.

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 ('Change a saved action's status, priority or assignee in this project') and names the three mutable fields, so an agent knows exactly what the tool targets. It does not distinguish itself from close siblings like edit_action, move_action or dismiss_action, which the phrase 'status ... dismissed' partially overlaps.

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: it directs the agent to use ids 'returned by list_actions' and explains the null-assignee case, but never says when to pick this over edit_action, move_action or dismiss_action. The dismissal-baseline note gives context for the 'dismissed' status but is not a selection rule.

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