Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_project_task

Manage project tasks in Freshservice: create, update, retrieve, filter, delete, add notes, and link associations to streamline project workflows.

Instructions

Manage Freshservice Project Tasks (NewGen).

    Tasks organize project work — epics, user stories, subtasks, etc.
    Each task has a type, status, priority, assignee, and can be linked
    to sprints, versions, and parent tasks.

    Args:
        action: One of 'create', 'update', 'get', 'list', 'filter',
                'delete', 'get_task_types', 'get_task_type_fields',
                'get_task_statuses', 'get_task_priorities',
                'create_note', 'list_notes', 'update_note', 'delete_note',
                'create_association', 'get_associations', 'delete_association'.
        project_id: Project ID (required for all actions).
        task_id: Task ID (required for get/update/delete and note/association ops).
        title: Task title (create — MANDATORY).
        description: Task description (HTML or plain text).
        type_id: Task type ID — obtain via get_task_types (create — MANDATORY).
        status_id: Task status ID — obtain via get_task_statuses.
        priority_id: Task priority ID — obtain via get_task_priorities.
        assignee_id: User ID to assign the task to.
        reporter_id: User ID of the reporter (defaults to creator).
        parent_id: Parent task/epic ID for subtasks.
        planned_start_date: ISO datetime (yyyy-mm-ddThh:mm:ssZ).
        planned_end_date: ISO datetime (yyyy-mm-ddThh:mm:ssZ).
        planned_effort: Effort string, e.g. '1w 2d 3h 4m'.
        story_points: Story points for the task.
        sprint_id: Sprint ID — obtain via manage_project get_sprints.
        version_id: Version ID — obtain via manage_project get_versions.
        custom_fields: Custom fields dict.
        note_id: Note ID (update_note / delete_note).
        content: Note content — HTML (create_note / update_note).
        module_name: Association module — 'tickets', 'problems',
            'changes', or 'assets' (association operations).
        ids: Entity IDs to associate (create_association).
        association_id: Entity ID to dissociate (delete_association).
        query: Filter query for 'filter' action. Format:
            "priority_id:3 AND created_at:>'2025-01-01'"
        filter: Predefined filter for 'list' — 'all', etc.
        page/per_page: Pagination.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNo
pageNo
queryNo
titleNo
actionYes
filterNo
contentNo
note_idNo
task_idNo
type_idNo
per_pageNo
parent_idNo
sprint_idNo
status_idNo
project_idNo
version_idNo
assignee_idNo
descriptionNo
module_nameNo
priority_idNo
reporter_idNo
story_pointsNo
custom_fieldsNo
association_idNo
planned_effortNo
planned_end_dateNo
planned_start_dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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 disclosing behavior, but it only lists actions and parameter requirements. It does not mention side effects of destructive operations (e.g., delete, delete_association), permissions required, or what the response contains, leaving significant behavioral gaps for a mutation-heavy tool.

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 opens with a concise context paragraph, then lists 27 parameters in a structured, readable way. While long, each parameter line carries necessary information, and the 'Args:' section prevents it from being an unstructured wall of text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (18 actions, 27 parameters, no annotations), the description covers all actions and parameters, includes a detailed query example, and explains how to fetch ID references. An output schema exists, so return values need not be in the description, but error handling, side effects, and alternative tool comparisons are missing.

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

Parameters5/5

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

Despite having zero schema description coverage, the description meticulously documents all 27 parameters, including mandatory conditions ('title (create — MANDATORY)', 'type_id (create — MANDATORY)'), formats (ISO datetime, planned_effort example, query format), and how to obtain reference IDs. This adds significant value beyond the bare 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 'Manage Freshservice Project Tasks (NewGen)' and enumerates the available actions (create, update, get, list, delete, etc.), making the tool's purpose explicit and specific. It distinguishes from siblings like manage_change_task by focusing on project tasks, though it does not explicitly compare with those sibling tools.

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?

It provides clear usage context for project task management and instructs on prerequisite steps, such as 'obtain via get_task_types' for type/status/priority IDs, which implies a workflow. However, it does not explicitly state when to use this tool over alternatives like manage_change_task or manage_problem_task.

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

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/forterro/freshservice_mcp'

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