AnalyticsProof

List saved journeys

list_journeys

Read-onlyIdempotent

List saved journeys (permission: read)

Saved journeys for the key's project, newest first. Filter with ?targetId= and ?status=. Each entry carries status (active unless paused), stepCount (counted steps), viewport, updatedAt, runOrder (execution order within the target) and quotaState — sleeping means the journey is ranked beyond the plan's per-target quota and will not be scheduled; over_step_cap means it has more steps than the plan's per-journey step limit and will not be scheduled. quotaState is the quota rank only: a journey runs when status is active, quotaState is running and the test's schedule is enabled. Keyset paginated: pass nextCursor as ?cursor=.

Read one journey's steps with get_journey; list_scans with journeyId lists its replays.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_journeys"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, 1–100.
`cursor`	No	The previous page's `nextCursor` (opaque). A malformed cursor is 400 on path cursor (issue code invalid_cursor).
`status`	No	Return only the journeys with this status (active: every journey that is not paused).
`targetId`	No	Return only the journeys linked to this scan target.
`projectId`	No	Required with an organization key; must be the key's project with a project key. Missing (organization key) or not a UUID: 400 invalid_request on path projectId; a project outside the key's reach: 404.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses default ordering (newest first), keyset pagination via nextCursor, and the semantics of quotaState values including the non-obvious fact that `sleeping` and `over_step_cap` journeys will not be scheduled. It also states the exact three-condition rule for when a journey actually runs, which an agent cannot infer from annotations.

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?

Front-loaded with purpose and scope, then return fields, then scheduling semantics, then sibling routing — a logical progression. The quotaState sentence is long and dense but each clause carries decision-relevant meaning; little is wasted, though it flirts with over-explaining enum states.

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?

There is no output schema, and the description compensates by enumerating the returned entry fields (status, stepCount, viewport, updatedAt, runOrder, quotaState) and their meanings. Combined with pagination and filtering guidance, nothing an agent needs to call or interpret 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%, so the schema already explains limit, cursor, status, targetId and projectId, including the projectId auth failure modes. The description only restates the filter parameters and the cursor mapping (`nextCursor` as `?cursor=`), adding no behavioral detail beyond the schema. 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?

Opens with a specific verb and resource ("List saved journeys") and immediately scopes it to "the key's project, newest first". It also names the sibling tools that serve adjacent needs (get_journey for steps, list_scans for replays), so an agent can distinguish it from get_journey and list_scans without opening any 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?

Gives concrete filter entry points (`?targetId=` and `?status=`) and routes the agent to alternatives for related data: get_journey to read one journey's steps and list_scans with journeyId for replays. It lacks an explicit "do not use this when…" exclusion, but the selection context is unambiguous.

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

All AnalyticsProof 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?