Ranksmile

Actions

actions__list

Read-onlyIdempotent

Recommended actions for this workspace, highest impact first: goal site (fix the site), owned (write or improve a page), earned (get onto an outside page: surface editorial, ugc or reference) or claims (correct what answers say). Each with impact (1-5), status (new, in_progress, done, declined), topic and steps done. actions__get has the details.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "actions__list"
  }
}

Input Schema

Name	Required	Description
`goal`	No
`limit`	No	Max rows, 1-100 (default 20).
`offset`	No	Rows to skip (default 0). Keep paging while has_more is true.
`status`	No
`surface`	No
`workspace_id`	Yes	From workspace__list.

Output Schema

Name	Required	Description
`counts`	Yes	by_goal and by_status, over all actions of the site.
`domain`	Yes
`actions`	Yes	id, goal, surface, kind, platform, page_type, status, impact, title, topic, models, steps, steps_done, created_at, done_at.
`has_more`	Yes
`workspace_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful ordering ('highest impact first') and the shape of each row (impact 1-5, status, topic, steps done), but says nothing about result volume or that paging continues while has_more is true — that lives only in the schema's offset description.

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?

Dense and front-loaded — the core purpose and ordering come first, then the categories, then the routing hint. It is close to a run-on sentence with a long parenthetical list, but no sentence is wasted.

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 needn't be explained, and the description still names the fields an agent will see. Combined with annotations and the enum explanations, an agent has enough to call it correctly; only surface semantics and paging behavior are left thin.

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?

With 50% schema coverage, the description compensates by explaining what the goal enum values mean ('site (fix the site), owned (write or improve a page), earned ... claims ...'), which the bare enum strings do not convey. It also lists the status values. It doesn't clarify surface values or how goal/surface interact, leaving a small gap.

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+resource: 'Recommended actions for this workspace, highest impact first', then names the four goal categories that scope it. It explicitly distinguishes itself from actions__get ('actions__get has the details'), so an agent can separate the list and detail tools 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?

Routes the agent to actions__get for detail, which is a clear alternative-and-condition hint. It also implies when to use it (reviewing recommended work in a workspace) but doesn't state exclusions or prerequisites, such as whether workspace_id must come from workspace__list (that lives only in the schema).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ranksmile tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?