Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

delete_ticket_summary

Remove ticket summaries in Freshdesk using a specified ticket ID to streamline support ticket management and maintain cleaner records.

Instructions

Delete the summary of a ticket in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYes

Implementation Reference

  • The main handler function for the 'delete_ticket_summary' tool. It sends a DELETE request to the Freshdesk API to remove the summary of the specified ticket. Includes error handling and success response formatting. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    async def delete_ticket_summary(ticket_id: int) -> Dict[str, Any]:
        """Delete the summary of a ticket in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/tickets/{ticket_id}/summary"
        headers = {
            "Authorization": f"Basic {base64.b64encode(f'{FRESHDESK_API_KEY}:X'.encode()).decode()}",
            "Content-Type": "application/json"
        }
    
        async with httpx.AsyncClient() as client:
            try:
                response = await client.delete(url, headers=headers)
                if response.status_code == 204:
                    return {"success": True, "message": "Ticket summary deleted successfully"}
    
                response.raise_for_status()
                return response.json()
            except httpx.HTTPStatusError as e:
                return {"error": f"Failed to delete ticket summary: {str(e)}"}
            except Exception as e:
                return {"error": f"An unexpected error occurred: {str(e)}"}
  • The @mcp.tool() decorator registers the delete_ticket_summary function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a deletion operation but doesn't mention whether this action is reversible, what permissions are required, or what happens to related data. For a destructive operation, this lack of safety and behavioral context is a significant gap.

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, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple operation and front-loads the essential information.

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?

For a destructive operation with no annotations and no output schema, the description is incomplete. It doesn't address critical context like whether the deletion is permanent, what confirmation might be needed, or what the response contains. Given the complexity of a delete operation in a ticketing system, more behavioral guidance is warranted.

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?

The description doesn't provide any parameter information beyond what's implied by the tool name. With 0% schema description coverage and only one parameter (ticket_id), the baseline is 4 for zero parameters, but since there is one parameter that isn't explained in the description, it drops to 3. The schema alone documents the parameter type and requirement.

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 action ('Delete') and the resource ('summary of a ticket in Freshdesk'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'delete_ticket' or 'update_ticket_summary', which would be helpful for precise tool selection.

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 like 'delete_ticket' (which deletes the entire ticket) or 'update_ticket_summary' (which modifies it). Without this context, an agent might struggle to choose between these similar-sounding operations.

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

Related 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/effytech/freshdesk_mcp'

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