Skip to main content
Glama

devin_request

Destructive

Run a Cognition Devin CLI request synchronously with headless print mode, configurable permissions, sandboxing, session resume, and ACP transport for summarization or code review.

Instructions

Run a Cognition Devin CLI request synchronously (auto-defers to a pollable job past the sync deadline when async jobs are enabled; otherwise runs to completion). Headless print mode (devin -p).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel name or alias (e.g. opus, latest)
configNoConfig file path (Devin --config <PATH>)
promptNoPrompt text for Devin CLI. Required in practice; promptFile is additive (loads an initial prompt from a file).
sandboxNoRun the Devin session in a sandbox (Devin --sandbox). Safety control: never defaulted on; pass true to opt in.
agentTypeNoACP agent variant for transport=acp (`devin acp --agent-type`): 'summarizer' (no tools, text summary) or 'review' (read-only + shell code-review). Ignored for the CLI transport.
sessionIdNoDevin session ID to resume (emits --resume <id>; use resumeLatest for --continue). Note: the gw-* id minted for a brand-new session is not resumable via sessionId; continue with resumeLatest:true.
transportNoTransport: 'cli' (default) runs the Devin CLI; 'acp' routes through `devin acp` when [acp].enabled and the provider's runtime_enabled are set (fails closed otherwise).cli
promptFileNoLoad the initial prompt from a file (--prompt-file)
agentConfigNoAgent config file path (Devin --agent-config <FILE>)
forceRefreshNoBypass dedup and force a fresh CLI run even if a recent identical request exists
resumeLatestNoResume the most recent Devin session in cwd (--continue). Note: the gw-* id minted for a brand-new session is not resumable via sessionId; continue with resumeLatest:true.
correlationIdNoRequest trace ID (auto if omitted)
exportSessionNoExport the session (Devin --export [<PATH>]). true emits a bare --export; a string path emits --export <path>.
idleTimeoutMsNoIdle timeout in ms (min 30s, max 1h, omit=CLI default)
optimizePromptNoOptimize prompt before execution
permissionModeNoDevin CLI permission mode (--permission-mode). auto auto-approves read-only tools; smart additionally auto-runs actions a fast model judges safe; dangerous auto-approves all. When omitted, Devin uses its own headless default; pass auto or smart for unattended runs.
compressResponseNoCompress the response display text via the native compressor (default: [compression].enabled in config.toml, off unless opted in). Skipped for structured output.
createNewSessionNoForce a new session
optimizeResponseNoOptimize response output
respectWorkspaceTrustNoRespect workspace trust (Devin --respect-workspace-trust <bool>). Devin defaults true for interactive and false for print mode; set explicitly to override.
Behavior4/5

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

Annotations already mark this as potentially destructive (destructiveHint=true). The description adds key behavioral details: synchronous execution with auto-deferral and headless print mode. This provides useful context beyond annotations.

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 two sentences, front-loads the core action, and contains no extraneous 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's complexity (20 parameters, no output schema), the description lacks important context such as return value format or behavior for different transports. It does not explain what the response looks like, which is a notable gap.

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 100%, so the schema fully documents parameters. The description adds no extra parameter meaning, meeting the baseline expectation.

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 runs a Devin CLI request synchronously, using specific verbs and nouns. It distinguishes from the async sibling by mentioning auto-deferral behavior when async jobs are enabled.

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 implies when to use (synchronous context) but does not explicitly state when to prefer this over alternatives like devin_request_async. No usage exclusions or alternative pointers are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/verivus-oss/llm-cli-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server