cursor-api-mcp

download_agent_artifact

Generate a presigned URL to download an artifact from a Cursor Agent using its ID and file path.

Instructions

Get a 15-minute presigned URL for an artifact (GET .../artifacts/download).

Args: agent_id: Agent id (for example bc-...). path: Relative artifact path from list_agent_artifacts (for example artifacts/screenshot.png).

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": {
      "agent_id": "<agent_id>",
      "path": "<path>"
    },
    "name": "download_agent_artifact"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`agent_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description discloses the presigned URL expiration (15 minutes) and the HTTP method, providing useful behavioral context. However, it omits potential side effects, authorization requirements, or rate limits. With no annotations, the description carries the burden, and while it adds value, it is not fully transparent.

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?

The description is concise with two short sentences and a bullet-like list of arguments. No extraneous information. The key action and parameters are front-loaded. Slightly more compact could be achieved, but it is efficient overall.

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?

Given the presence of an output schema (not shown), the description adequately covers the tool's function and parameters. However, it lacks usage guidelines, error handling, and behavioral context like permissions. For a tool with no annotations, it is moderately complete but has gaps.

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 0%, so the description must add meaning. It provides examples for both agent_id ('bc-...') and path (relative path from list_agent_artifacts). This adds context beyond the bare schema, but could be more precise about formats or constraints. It compensates partially but not fully.

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?

The description clearly states it returns a 15-minute presigned URL for an artifact, specifying the HTTP method and endpoint. This is a specific verb+resource. However, it does not explicitly differentiate from sibling tools like download_ai_code_commits, though the context of artifacts versus code commits provides some distinction.

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 guidance on when to use this tool versus alternatives, such as direct download or other artifact operations. There are no prerequisites, exclusions, or alternatives mentioned, leaving the agent without context to choose correctly among siblings.

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

Deploy Server