Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_project

Manage Freshservice project lifecycles by creating, updating, listing, and archiving projects, plus managing sprints, members, and associations with tickets, changes, problems, and assets.

Instructions

Manage Freshservice Projects (NewGen).

    Projects let you plan, prioritize, manage, and track work within
    the service desk. You can associate tickets, changes, problems,
    and assets to projects.

    Args:
        action: One of 'create', 'update', 'get', 'list', 'delete',
                'archive', 'restore', 'get_fields', 'get_templates',
                'add_members', 'get_memberships',
                'create_association', 'get_associations', 'delete_association',
                'get_versions', 'get_sprints'.
        project_id: Project ID (required for most actions except create,
            list, get_fields, get_templates).
        name: Project name (create — MANDATORY, max 255 chars).
        description: Project description (HTML or plain text).
        key: Project key — starts with letter, letters+numbers, max 10 chars.
            Auto-generated from name if omitted on create.
        project_type: 0=Software, 1=Business (create — MANDATORY).
        status_id: 1=Yet to start, 2=In Progress, 3=Completed.
        priority_id: 1=Low, 2=Medium, 3=High, 4=Urgent.
        manager_id: User ID of the project manager.
        start_date: Start date (yyyy-mm-dd).
        end_date: End date (yyyy-mm-dd).
        visibility: 0=Private, 1=Public (default 1).
        sprint_duration: Sprint duration in days (default 14).
        custom_fields: Custom fields dict.
        project_template_id: Template ID (create only).
        members: List of members to add (add_members).
            Format: [{"email": "user@example.com", "role": 1}]
            role: 1 or 2 (project admin vs member).
        module_name: Association module — 'tickets', 'problems',
            'changes', or 'assets' (create/get/delete_association).
        ids: List of IDs to associate (create_association).
        association_id: Entity ID to dissociate (delete_association).
        filter: Filter for list — 'completed', 'incomplete', 'archived',
            'open', 'in_progress'. Default shows open + completed.
        page/per_page: Pagination (list, max 100 per page).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNo
keyNo
nameNo
pageNo
actionYes
filterNo
membersNo
end_dateNo
per_pageNo
status_idNo
manager_idNo
project_idNo
start_dateNo
visibilityNo
descriptionNo
module_nameNo
priority_idNo
project_typeNo
custom_fieldsNo
association_idNo
sprint_durationNo
project_template_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It lists actions like delete, archive, and restore, but does not disclose side effects, irreversibility, permission requirements, or rate limits. The parameter-focused text adds constraints and defaults, but stops short of explaining the consequences of actions.

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 long but necessarily so, given the tool's 22 parameters and 16 actions. It is well-structured with a clear 'Args:' list and each entry adds value. It could be slightly more concise, but overall it is organized and scannable.

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

Completeness5/5

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

Given the tool's complexity, the description is remarkably complete: it covers all actions, required vs. optional parameters, defaults, filters, pagination limits, and data formats. It also clarifies association modules and member role semantics. The presence of an output schema means return values needn't be detailed here.

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?

The description provides exhaustive parameter semantics beyond the input schema: types, mandatory flags, max lengths, defaults, formats, and action-specific applicability. For example, it specifies that key auto-generates from name, visibility defaults to 1, and members follow a specific email/role structure. This fully compensates for the schema's 0% description coverage.

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 clearly defines the tool as a comprehensive manager for Freshservice Projects, enumerating 16 distinct actions from create to delete and associations. It explicitly scopes the resource to 'Projects (NewGen)' and distinguishes from sibling tools like manage_project_task by focusing solely on project-level operations.

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?

The description gives detailed usage context, explaining which actions exist and which parameters are required for each (e.g., project_id required for most actions except create, list, get_fields, get_templates). It provides defaults and filters, but does not explicitly mention alternative sibling tools or when to avoid this tool, so it lacks the explicit exclusion guidance of a 5.

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