DevTune MCP

devtune_list_agent_picks_runs

Read-onlyIdempotent

List the setup's own Agent Picks runs, newest first by created_at then id. Optional test_id narrows to an owned test, whichever setup it belongs to. Includes starter and paid history, never cloned public results or source artifacts. Pass pagination.next_cursor verbatim as cursor until has_more is false. Requires Agent Picks and visibility.read. Operational records only; use the summary for rates. stage is sandbox, setup, agent or judging while running, otherwise null, including older runs. During agent, model_calls reports proxy-recorded calls across attempts; null means no meter was recorded. cell_agreed=true marks a run cancelled before it started because its cell's first 4 runs picked the same thing: not needed, not an error or missing coverage, and not charged. Cannot start or change a run.

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

Input Schema

Name	Required	Description
`limit`	No	Results per page.
`setup`	No	The Agent Picks setup to use: its id or its category slug. Optional while the project has one setup. With several, omitting it is refused as agent_picks_setup_required, and a setup the project does not have as agent_picks_setup_not_found; both list the project setups in details.setups (id, category_slug, category_name). The response echoes the setup used as setup {id, category_slug}.
`cursor`	No
`test_id`	No
`pageSize`	No	The same setting as limit. Send either.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 10, 2026
- removedInput schema / properties / pageSize / $ref
```
Removed value: -"#/properties/limit"
```
- addedInput schema / properties / pageSize / maximum
```
Added value: +100
```
- addedInput schema / properties / pageSize / minimum
```
Added value: +1
```
- addedInput schema / properties / pageSize / type
```
Added value: +"integer"
```
- addedInput schema / properties / test_id / 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})$"
```

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / setup

Added value: +{
+  "description": "The Agent Picks setup to use: its id or its category slug. Optional while the project has one setup. With several, omitting it is refused as agent_picks_setup_required, and a setup the project does not have as agent_picks_setup_not_found; both list the project setups in details.setups (id, category_slug, category_name). The response echoes the setup used as setup {id, category_slug}.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

Changed3 schema fields changedOct 25, 2026
- removedInput schema / properties / limit / default
```
Removed value: -50
```
- addedInput schema / properties / limit / description
```
Added value: +"Results per page."
```
- addedInput schema / properties / pageSize
```
Added value: +{
+  "$ref": "#/properties/limit",
+  "description": "The same setting as limit. Send either."
+}
```
AddedOct 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish a safe read (readOnly, idempotent, non-destructive), yet the description adds substantial behavior beyond them: prerequisite scopes, the cursor/next_cursor/has_more pagination contract, stage values and when stage is null, model_calls being proxy-recorded per attempt with null meaning no meter, and cell_agreed=true denoting a pre-start cancellation that is not an error or charge. That is exactly the kind of context annotations cannot carry.

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 the core action and ordering, then progressive detail. Sentences are dense but each contributes a distinct fact; the enumeration of stage, model_calls, and cell_agreed reads as reference material rather than padding. Slight overloading of one paragraph with return-field semantics keeps it from a 5.

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?

With no output schema, the description usefully explains the notable returned fields (stage, model_calls, cell_agreed) and the pagination loop, and it names the required scopes. It does not describe the overall record shape or the response envelope for next_cursor/has_more beyond implying them, leaving a small gap for a 5-parameter list tool.

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?

Schema coverage is 60%, with cursor having no schema description at all; the description compensates by specifying that pagination.next_cursor must be passed verbatim and repeated until has_more is false, and adds ownership semantics for test_id ('an owned test, whichever setup it belongs to'). limit/pageSize and the setup id-vs-slug behavior remain schema-only, so it adds value without fully covering the parameter set.

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 with scope and ordering: 'List the setup's own Agent Picks runs, newest first by created_at then id.' It further bounds scope by declaring what is excluded ('never cloned public results or source artifacts'), which lets an agent separate this from devtune_list_agent_runs and from the single-run getter.

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 routing: use the summary for rates, and use test_id to narrow to an owned test. It also states prerequisites ('Requires Agent Picks and visibility.read') and disclaims capability ('Cannot start or change a run'). No explicit when-not-to-use versus devtune_list_agent_runs or devtune_get_agent_picks_history, so it falls short of full routing.

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?