Skip to main content
Glama

Visibility Genies

List actions

list_actions
Read-onlyDestructive

Read saved project actions in the order the Actions page shows them, with their practical steps, pages, due day, evidence date, assignment and status. Uses no credits or provider calls. Suggested work comes from saved audit, prompt, Perception, Search Console and gap evidence. Optional filters by status, source, subject, assignee and due day, and pagination, do not change the saved work. get_action reads one action with its notes and change history.

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>"
    },
    "name": "list_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueToNoOnly actions due on or before this day, YYYY-MM-DD.
limitNo
offsetNo
sourceNo
statusNo
dueFromNoOnly actions due on or after this day, YYYY-MM-DD.
assigneeNoA member id from assignees, to list that person's actions, or 'unassigned'.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
sourceSubjectNo

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsYes
assigneesYes
totalCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond readOnlyHint the description discloses cost behavior ('Uses no credits or provider calls'), ordering guarantees, the provenance of suggested work, and the important reassurance that filters and pagination 'do not change the saved work'. That is genuine added context. The annotations pair readOnlyHint=true with destructiveHint=true, and the description leans entirely read-only without addressing that tension, which keeps it from a 5.

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 first sentence front-loads what is returned, and the alternative-routing sentence is placed last where it is easy to catch. The provenance sentence about audit, prompt, Perception, Search Console and gap evidence is somewhat list-heavy for the value it adds, but no sentence is redundant.

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?

An output schema exists, so return values need no explanation, and the description still covers ordering, cost, filter neutrality and the sibling relationship. The main residual gap is filter semantics for the less-documented parameters, but for a paginated read-only list this is close to sufficient.

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 schema coverage at 44%, the description partially compensates by naming the filter dimensions (status, source, subject, assignee, due day) and pagination. However it adds no format or value semantics for the weakly documented fields — sourceSubject has no schema description and the description only says 'subject', and it never explains 'unassigned' or the date-boundary behavior of dueFrom/dueTo. It enumerates parameters without deepening their meaning.

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 gives a specific verb and resource (read saved project actions) plus the exact shape of the returned records: practical steps, pages, due day, evidence date, assignment and status. It also closes by distinguishing itself from get_action, so an agent can tell the list tool apart from the single-record tool without opening 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 Guidelines4/5

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

It names the sibling alternative explicitly ('get_action reads one action with its notes and change history'), which gives a clear routing rule for single-action vs. list use, and notes the ordering matches the Actions page. It stops short of stating when not to use it (e.g., an archived project, or when a direct ID is already known), so it falls just short of a full 5.

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