Skip to main content
Glama
Sign In
cursor-sdk-mcp

cursor-sdk-mcp

by newxun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cursor: follow up

cursor_follow_up
Destructive

Resume a Cursor Agent conversation using its agent ID and a new prompt. Automatically loads prior context for coherent interaction.

Instructions

Continue an existing Cursor Agent conversation by agentId with a new prompt. Conversation context from previous runs is loaded automatically.

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": {
      "agentId": "<agentId>",
      "prompt": "<prompt>"
    },
    "name": "cursor_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe agentId returned by a previous cursor_run_agent call.
promptYesFollow-up instruction for the agent.
modelNoOptional per-run model override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide destructiveHint=true; description adds automatic context loading. Additional behavioral details like mutation effects are omitted.

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?

Two concise sentences with zero waste, front-loading the core purpose.

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?

No output schema provided and description lacks return value details. Adequate for simple follow-up but incomplete for understanding full tool behavior.

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 covers 100% of parameters with descriptions. Description adds no further meaning beyond restating schema.

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?

Description clearly states it continues an existing conversation via agentId with a new prompt, distinguishing it from sibling cursor_run_agent which starts new conversations.

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

Usage Guidelines4/5

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

Implies use after cursor_run_agent by requiring agentId. Provides context but no explicit when-not-to-use alternatives.

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

Deploy Server

Other Tools