Skip to main content
Glama
effytech

Freshdesk MCP server

by effytech

list_canned_responses

Retrieve all canned responses from Freshdesk for efficient ticket management. Specify folder_id to organize and access pre-written support replies.

Instructions

List all canned responses in Freshdesk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes

Implementation Reference

  • The handler function for the 'list_canned_responses' tool. It fetches canned responses from a specified folder in Freshdesk using the API, decorated with @mcp.tool() for registration in the MCP server.
    @mcp.tool()
    async def list_canned_responses(folder_id: int)-> list[Dict[str, Any]]:
        """List all canned responses in Freshdesk."""
        url = f"https://{FRESHDESK_DOMAIN}/api/v2/canned_response_folders/{folder_id}/responses"
        headers = {
            "Authorization": f"Basic {base64.b64encode(f'{FRESHDESK_API_KEY}:X'.encode()).decode()}"
        }
        canned_responses = []
        async with httpx.AsyncClient() as client:
            response = await client.get(url, headers=headers)
            for canned_response in response.json():
                canned_responses.append(canned_response)
        return canned_responses
  • The @mcp.tool() decorator registers the list_canned_responses 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 the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't mention pagination, rate limits, authentication needs, or what 'all' entails (e.g., scope limitations). This leaves significant gaps for a tool with one required parameter.

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 with zero waste. It's appropriately sized for a simple list tool and front-loaded with the core purpose, making it easy to parse quickly.

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 no annotations, 0% schema coverage, no output schema, and one required parameter, the description is incomplete. It lacks details on parameter semantics, behavioral traits like pagination or errors, and doesn't help distinguish from sibling tools, making it inadequate for reliable tool selection and invocation.

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%, so the description must compensate for the undocumented parameter 'folder_id'. The description adds no information about parameters, failing to explain what 'folder_id' is, its purpose, or how it affects the listing. This leaves the parameter's meaning unclear.

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 ('List all') and resource ('canned responses in Freshdesk'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_canned_response_folders' or 'view_canned_response', which would require mentioning scope or format differences.

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 'view_canned_response' or 'list_canned_response_folders'. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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