Skip to main content
Glama

Visibility Genies

Create an action

create_action

Adds one action to the project's Actions page, in Suggested, labelled as added by your agent: a title, why it matters, the steps and the pages it affects. Ask the user before adding actions. Each call adds one action; at most 20 a project each day. Refreshes never change or reopen it, and the user moves it to To do, done or dismissed. Free: buys nothing. Returns the action's id for update_action.

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>",
      "title": "<title>",
      "why": "<why>",
      "steps": "<steps>"
    },
    "name": "create_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyYesWhy it matters, with the evidence you found.
urlsNoThe pages it affects, if any.
stepsYesThe steps to do it, in order, one per item.
titleYesWhat to do, as a short task, 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.4/5.0
Behavior5/5

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

Annotations only mark it as a non-destructive write; the description goes well beyond that, disclosing the created state (Suggested), attribution labelling, the lifecycle rule that refreshes never change or reopen it, that the user moves it to To do/done/dismissed, the daily cap, and cost behaviour ('Free: buys nothing'). That is exactly the context an agent needs before a mutation.

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?

The definition is front-loaded with purpose and packed with high-value facts, with no filler sentences. It is dense to the point of reading as comma-joined clauses, which slightly hurts scanability, but every sentence carries information.

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?

For a 5-parameter mutation with an output schema, this covers purpose, confirmation requirement, quota, resulting state, cost, and the id returned for chaining. Nothing an agent needs in order to call it 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 coverage is 100%, so every parameter already carries its own description. The prose enumerates the same fields (title, why, steps, pages) but adds no format, ordering, or constraint detail beyond what the schema states, so the baseline 3 applies.

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?

The description opens with a concrete verb and resource ('Adds one action to the project's Actions page') and immediately pins down the resulting state ('in Suggested, labelled as added by your agent') plus the payload fields. An agent can distinguish this from update_action, which the description explicitly routes to, without opening the schema.

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?

It gives a clear behavioural precondition ('Ask the user before adding actions') and a quota ('at most 20 a project each day'), and names update_action as the follow-up path once you have the returned id. It stops short of saying when not to create an action versus using another sibling, but the preconditions are explicit.

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