Skip to main content
Glama

Visibility Genies

Move an action

move_action

Move a saved action up or down within its own status column on the Actions board, such as To do. To move it to another column, use update_action with a status. 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>",
      "position": "<position>"
    },
    "name": "move_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
positionYesIts new place within its own status column, 0 for the top. A number past the end puts it last.
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation-without-destruction profile is known. The description adds genuinely new context beyond that: there are no credit costs or provider calls, and the move is constrained to the action's current column, which tells the agent no external side effects or cross-column state changes occur. It stops short of saying the change is reversible or how ordering ties are resolved.

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 with zero filler. The primary capability is front-loaded and the alternative-tool redirect follows immediately, so the agent gets both the action and the fallback in one pass.

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 and all three parameters fully documented in the schema, the description only needs to cover scope, cost, and tool selection, all of which it does. Nothing needed to invoke this tool correctly is missing.

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 schema already explains that position is zero-based within the status column and that out-of-range values place the action last. The description's phrase 'within its own status column' reinforces but does not extend the parameter meaning, so the baseline 3 is appropriate.

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 with explicit scope: reordering a saved action within its own status column on the Actions board. It also names the sibling update_action for the different operation of changing columns, so an agent can distinguish the two without reading either schema.

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

Usage Guidelines5/5

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

Gives both the when-to-use ('reorder within its status column') and the when-to-use-something-else condition ('to move it to another column, use update_action with a status'). The routing decision is fully specified with no inference required.

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