DevTune MCP

devtune_list_visibility_responses

Read-onlyIdempotent

List the latest 20 successful AI executions in this project, optionally filtered by prompt or platform. Pass an executionId to devtune_get_visibility_response to inspect retained answer and ad evidence. This is an operational listing, not a measurement sample; use visibility summary for rates.

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": "devtune_list_visibility_responses"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	No
`promptId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / promptId / pattern
```
Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
```
AddedSep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: only the latest 20, only successful executions, and that records are "retained" rather than exhaustive. It stops short of describing entry shape or ordering/pagination, but the hard 20-item cap makes pagination moot.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: capability and cap first, then the drill-down route, then the disambiguation from the summary tool. No filler and nothing buried.

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?

For a read-only list tool with no output schema and four annotations, the description covers scope, cap, filters, and next step. It leaves the shape of a listed execution (what identifies each row) implicit, which is a minor gap given no output schema exists.

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 0%, so the description must carry parameter meaning, and it does name both filters (prompt, platform) as optional. However it adds no matching semantics (exact vs. partial, case sensitivity) beyond the schema's format/length constraints, and the executionId mention belongs to the sibling tool rather than this tool's parameters.

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 and resource ("List the latest 20 successful AI executions in this project"), including the result cap and the available filters. It also distinguishes itself from devtune_get_visibility_response (drill-down) and the visibility summary (rates), so an agent can place it among its siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit routing: use this for operational listing, pass the executionId to devtune_get_visibility_response to inspect retained answer/evidence, and use the visibility summary if rates are wanted. Both the positive case and the two excluded cases are named.

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

All DevTune MCP 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?