Pingstack

List dashboards

list_dashboards

Read-onlyIdempotent

List the account's dashboards, including the built-in Overview, oldest first, 20 per page. Each item has the dashboard id, name, assignable (false for Overview, which always shows every check and can't be changed) and public. It's a directory of dashboards: the checks, sections and display settings of each one aren't included. public_url and public_wallboard_url are the links anyone can open, set only while the dashboard is public; otherwise both are null. domain_url and domain_wallboard_url are set when a public dashboard is also served on its own verified subdomain or custom domain. An account always has at least Overview. next_cursor is null on the last page.

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_dashboards"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Items per page, 1 to 100. Defaults to 20.
`cursor`	No	next_cursor from the previous page. Omit for the first page; next_cursor is null on the last.

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only annotations, it discloses ordering (oldest first), default page size, pagination termination via next_cursor null, and the guarantee that Overview always exists. It also explains the semantics of assignable, public_url, public_wallboard_url, domain_url, and domain_wallboard_url, which are meaningful behavioral details for interpreting results.

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 description is front-loaded with the core purpose and then supplies dense, relevant details. It is somewhat long because it explains several output-field semantics despite an output schema existing, but each sentence is informative rather than filler.

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 paginated read-only list tool with annotations and an output schema, the description is complete: it covers scope, ordering, pagination, the always-present Overview dashboard, and key field conditions. An agent should be able to call it and interpret the result correctly.

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 limit and cursor are already well documented in the schema. The description adds ordering and restates that next_cursor is null on the last page, but does not add much parameter-level meaning beyond the schema.

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 states a specific verb and resource: list the account's dashboards. It also distinguishes this directory-style operation from detail-oriented siblings by explicitly saying checks, sections, and display settings are not included.

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?

The description makes clear this is a directory listing rather than a detail fetch, which implicitly routes agents to get_dashboard for per-dashboard contents. It does not explicitly name get_dashboard or state when not to use this tool, so it falls short of a full when/when-not/alternatives guide.

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

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