Tools
List a tool's recent calls
Returns the tool’s newest calls — status, timing, cost and token usage, and the governance disposition. Requires permission agents:read.
GET
List a tool's recent calls
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/tools/listExecutions?id=<toolId>[&limit=<n>&cursor=<cursor>] lists a tool’s calls, newest first, as the tool detail page’s activity does.
Authority
You needagents:read at the platform scope; a grant at an org unit alone is a recorded 403. Each call is then fenced on its own: the calling agent (agentId) appears only when you can read that agent, the run and step (runId, stepId) only when you can read the run, and the summaries and error only when you can read the parent run. A missing, draft or archived tool answers 404 resource_missing; an unavailable store is a 500, never a 404. A repeated or malformed parameter, or a cursor from another request, is 400 bad_request.
What it returns
Each call carries itsstatus, startedAt, completedAt, durationMs, costCents, token usage, governanceDisposition, refusalReason and commandTier. inputSummary, outputSummary and error are at most 500 characters with secrets masked; when they are withheld, contentWithheld is true. A chat, factory or debug call always withholds its content, and a call whose run cannot be decided withholds its run, step and content. The raw input and output are never returned.
Calls come a page at a time (limit 1–100, default 50; a larger limit reads 100). While meta.hasMore is true, pass meta.nextCursor as cursor with the same other parameters for the next page. A page may hold fewer calls than limit while more remain; the list never answers meta.partial.Authorizations
Query Parameters
Response
List a tool's recent calls

