Freshdesk MCP Server

by Sidd07Dev

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

create_outbound_email

Create and send outbound emails in Freshdesk with support for cc, bcc, tags, and custom fields.

Instructions

Create and send an outbound email from Freshdesk. Supports cc, bcc, tags, and custom fields.

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": {
      "email": "<email>",
      "subject": "<subject>",
      "description": "<description>",
      "email_config_id": "<email_config_id>"
    },
    "name": "create_outbound_email"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`email`	Yes
`status`	No
`subject`	Yes
`priority`	No
`cc_emails`	No
`bcc_emails`	No
`description`	Yes
`workspace_id`	No
`custom_fields`	No
`email_config_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, and the description only states 'Create and send' with no details on expected behavior (e.g., idempotency, error conditions, permission requirements). It adds little beyond the fact that it's a write operation.

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 a single sentence that efficiently states purpose and key supported fields. It front-loads the core action, but could be slightly more structured (e.g., separating purpose and supported features). No filler.

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 11 parameters, 4 required, and an output schema, the description is too sparse. It does not explain the output, prerequisites (e.g., email_config_id configuration), or the broader workflow context (e.g., relationship to tickets or contacts).

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions cc, bcc, tags, and custom fields by name without explaining their purpose, format, or relationships. Required parameters (email, subject, description, email_config_id) are not elaborated, so the description adds minimal semantic value beyond the schema.

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 the tool creates and sends an outbound email from Freshdesk and lists supported features (cc, bcc, tags, custom fields). However, it could more explicitly distinguish this from sibling tools like reply_ticket, and clarify whether the email is tied to a ticket or standalone.

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 (e.g., reply_ticket). The description does not include when-not-to-use or prerequisites like email_config_id meaning.

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