Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_release

Manage Freshservice releases by creating, retrieving, updating, deleting, filtering, and restoring them. Control release details, scheduling, assignments, and planning fields.

Instructions

Manage Freshservice releases.

    NOTE: Like changes, planning_fields cannot be set on create.
    If you supply them, they will be applied via a follow-up PUT
    automatically.

    Args:
        action: One of 'list', 'get', 'create', 'update', 'delete',
                'filter', 'restore', 'get_fields'.
        release_id: Release ID (required for get/update/delete/restore).
        subject: Release subject (required for create).
        description: HTML description (required for create).
        priority: 1=Low, 2=Medium, 3=High, 4=Urgent (required for create).
        status: 1=Open, 2=On hold, 3=In Progress, 4=Incomplete, 5=Completed
                (required for create).
        release_type: 1=Minor, 2=Standard, 3=Major, 4=Emergency
                      (required for create).
        planned_start_date: ISO datetime for planned start.
        planned_end_date: ISO datetime for planned end.
        work_start_date: ISO datetime for actual work start.
        work_end_date: ISO datetime for actual work end.
        agent_id: Assigned agent ID.
        group_id: Assigned group ID.
        department_id: Department ID.
        category/sub_category/item_category: Categorization.
        assets: Associated assets [{"display_id": N}].
        planning_fields: Planning fields dict (build_plan, test_plan).
        custom_fields: Custom fields dict.
        query: Filter query for 'filter' action.
        page/per_page: Pagination.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryNo
actionYes
assetsNo
statusNo
subjectNo
agent_idNo
categoryNo
group_idNo
per_pageNo
priorityNo
release_idNo
descriptionNo
release_typeNo
sub_categoryNo
custom_fieldsNo
department_idNo
item_categoryNo
work_end_dateNo
planning_fieldsNo
work_start_dateNo
planned_end_dateNo
planned_start_dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses one useful non-obvious behavior: planning_fields cannot be set on create and are applied via a follow-up PUT. However, it lacks disclosure about other behavioral aspects such as destructive consequences of delete/restore, permission requirements, or rate limits.

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 front-loaded with purpose and the critical planning_fields note, followed by a well-organized Args list. It is long but every line carries necessary parameter documentation, so no waste.

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

Completeness3/5

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

For a 23-parameter tool with no annotations, the description covers all parameters and one key behavior, but omits query syntax, usage examples, and error handling. The output schema presumably covers return values, so that gap is acceptable.

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?

Every parameter is explained with meaningful detail beyond the schema, including numeric enum mappings (priority, status, release_type), required-on-create markers, formatting hints for assets, and the role of query for filter. This fully compensates for the 0% schema description coverage.

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 opening line 'Manage Freshservice releases' states a broad verb+resource, but the enumerated actions (list, get, create, update, delete, filter, restore, get_fields) clearly define the tool's scope. It is distinct from sibling tools targeting release notes, tasks, or time entries.

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 does not explicitly state when to use this tool versus alternatives like manage_release_note or manage_release_task. It implies usage through the action list but provides no guidance on tool selection or exclusions.

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