MCP_Salesforce

create_task

Create a new task in Salesforce with a subject, related record, due date, priority, and description. Use it to track follow-ups and manage sales activities.

Instructions

Create a new task in Salesforce

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": {
      "subject": "<subject>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description
`whoId`	No	Contact or Lead ID this task is related to
`whatId`	No	Account, Opportunity, or other record ID this task is related to
`dueDate`	No	Due date in YYYY-MM-DD format
`subject`	Yes	Task subject/title
`priority`	No	Task priority (High, Normal, Low)
`description`	No	Task description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a new task' and does not mention side effects, required permissions, whether the operation is reversible, or what the return value is. This is a significant gap for a mutation tool.

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 a single sentence with no filler: 'Create a new task in Salesforce.' Every word contributes to the purpose, and it is appropriately front-loaded.

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?

While the schema provides robust parameter documentation, the description lacks context about return values and how to obtain related record IDs (e.g., via search tools). No output schema exists, so the description should compensate, but it does not. The tool is simple enough that the schema plus description provide a minimally viable understanding, but gaps remain.

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 description coverage is 100% (all 6 parameters have descriptions), so the baseline is 3 even though the description itself adds no parameter detail. The description does not explain any parameter semantics beyond what the schema already provides.

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 'Create a new task in Salesforce' uses a specific verb ('Create') and identifies the resource ('task in Salesforce'). It clearly distinguishes from sibling tools like create_account, create_contact, and create_opportunity, which target different object types.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like needing to search for related records (whoId, whatId) first. There are no exclusions or context hints for the agent.

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

Deploy Server