freeagent-mcp-server

List Tasks

freeagent_list_tasks

Read-only

Retrieve FreeAgent tasks and filter them by view, project, or updated date to manage work items and track task status.

Instructions

List tasks from FreeAgent. Optionally filter by view, project, or updated_since.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "freeagent_list_tasks"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number to fetch (default 1)
`sort`	No	Sort order for tasks
`view`	No	Filter tasks by view: all, active, completed, or hidden
`project`	No	Project URL to filter tasks by
`per_page`	No	Results per page (default 25, max 100). Check pagination.next_page in the response for more results.
`updated_since`	No	Only return tasks updated since this date (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.0.0Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / page

Added value: +{
+  "description": "Page number to fetch (default 1)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per_page

Added value: +{
+  "description": "Results per page (default 25, max 100). Check pagination.next_page in the response for more results.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

First observedv1.3.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

readOnlyHint=true already covers the safety profile, so the description's burden is lower. It adds that results can be narrowed by filters but says nothing about pagination behavior, default result volumes, or ordering that the schema only partially hints at.

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?

Two short sentences with the operation stated first and the filtering capability second. Nothing is padded or redundant.

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?

A simple read-only list tool with full schema coverage and no output schema, so the description needs only to establish scope and filters, which it does. Only pagination expectations are left implicit.

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?

Schema description coverage is 100%, so every parameter's meaning is already documented in structured data. The description names three of six parameters but adds no syntax, format, or interaction detail beyond the schema, making the baseline 3 correct.

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?

States a specific verb+resource ('List tasks from FreeAgent'), which clearly separates it from the get/create/update/delete task siblings. It stops short of naming an alternative or scoping boundary, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Optionally filter by view, project, or updated_since' implies when the filters are useful but gives no explicit when-to-use vs when-not-to-use guidance, and no indication of when to page through results rather than filter. Adequate minimum, not prescriptive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server