Codex Control Plane MCP

Overview Schema Source Related Servers Discussions Admin

codex_start_review_workflow

Starts a durable code review workflow and returns an ID for progress polling. Automates code review for changes, commits, or branches.

Instructions

Start a durable Codex review workflow and return workflowId immediately. Use this for code review tasks. Next poll codex_get_workflow_status for progress and final report.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_type": "<target_type>"
    },
    "name": "codex_start_review_workflow"
  }
}

Input Schema

Name	Required	Default
`thread_id`	No
`project_id`	No
`cwd`	No
`target_type`	Yes
`base_branch`	No
`commit_sha`	No
`commit_title`	No
`instructions`	No
`delivery`	No
`client_request_id`	No
`model`	No
`sandbox`	No	read-only
`approval_policy`	No	on-request
`timeout_seconds`	No
`first_message_max_chars`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`agentGuidance`	No
`agentGuidanceText`	No
`recoveryAttemptState`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJun 19, 2026
- addedOutput schema / properties / agentGuidance
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
- addedOutput schema / properties / agentGuidanceText
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recoveryAttemptState
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
Addedv0.1.3Jun 18, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the workflow is durable and returns immediately, implying asynchronous behavior and need for polling. However, it does not mention side effects, state changes, or constraints like idempotency, which would be helpful for understanding the tool's impact.

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?

The description is extremely concise at three sentences with front-loaded purpose and clear follow-up action. No redundant information; every sentence adds value.

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

Completeness2/5

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

Given the tool has 15 parameters and an output schema, the description is incomplete. It omits guidance on how to configure parameters like target_type, sandbox, or instructions, which are essential for correct usage. The return value is partially covered by mentioning workflowId, but not fully detailed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description provides no information about the 15 parameters, their meanings, or how they affect behavior. This is a critical gap, as the agent must rely solely on the schema, which lacks descriptive text. The description should summarize key parameters like target_type and delivery.

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 clearly states the tool starts a durable Codex review workflow and returns a workflowId immediately. It specifies the action (start), the resource (review workflow), and the context (code review tasks), effectively distinguishing it from sibling tools like codex_start_plan_workflow and codex_start_chat.

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

Usage Guidelines3/5

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

The description tells users to use this tool for code review tasks and to poll codex_get_workflow_status afterward. However, it does not explicitly mention when not to use it or provide alternatives, such as when to use codex_start_plan_workflow instead, which is a guideline gap given the number of sibling tools.

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

Deploy Server