Skip to main content
Glama

codex_list

Read-onlyIdempotent

List and page persistent Codex tasks newest first, with compact or detailed supervision views and truncation indicators for large projections.

Instructions

Page persistent tasks, newest first. Large projections identify truncated_fields.

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

Input Schema

NameRequiredDescriptionDefault
viewNoDetail or compact supervision viewdefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two real behavioral facts beyond that: results are ordered newest-first, and large payloads flag truncation via truncated_fields. It does not say what happens at the limit boundary or whether paging is stable across writes.

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?

Two short sentences, front-loaded with the core listing behavior, with no filler. The second sentence is terse to the point of being cryptic, since truncated_fields is not explained, but it still earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the truncation signal is a useful addition. However, the default and maximum page size (50/200), the distinction between default and compact views, and the reliability of offset paging are all unexplained for a paginated tool.

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 coverage is only 33%; only 'view' is documented in the schema, and limit/offset have no descriptions. The single word 'Page' hints at limit/offset and 'projections' hints at view, but the description adds little concrete meaning beyond the enum and integer ranges the schema already supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with ordering: paging persistent tasks newest-first. It is clearly a listing tool, distinct from point-read siblings like codex_get, but it never names or contrasts any sibling, so differentiation is left implicit.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no alternatives named. An agent must infer that this is the bulk-listing counterpart to codex_get or codex_queue purely from the word 'Page'.

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