Skip to main content
Glama
Sign In

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

list_tasks

Read-only

List CRM tasks — work the team owes, like checking payment records, fixing a bug or sending a refund. Read-only. Tasks live in CRM → Tasks. A task may stand alone or be linked to contacts. While leads are on for the workspace, linking parks the contact's open lead until the task is done (parkLeads, default true), and marking the task done brings the linked leads back to Waiting on us so someone tells them the result (Won and Lost leads are left alone unless named in returnContactIds). Deleting a task, or unlinking a contact, brings a lead parked on it back to Waiting on us. A task is internal work for the team: nothing is sent to anyone. Each task lists its linked contacts with their lead status and whether the lead is parked on it.

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": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTasks to return, 1-200. Defaults to 50.
ownerNoeveryone (default), mine (needs a personal API key) or unassigned.
searchNoSubstring match on the title and notes.
statusNoOnly tasks in this status: todo, in_progress or done. Omit for all.
contactIdNoOnly tasks linked to this contact, as returned by list_contacts.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover the safety profile, yet the description adds substantial context beyond them: lead-parking semantics (parkLeads default true), what happens to parked leads when a task is completed, deleted, or unlinked, that Won/Lost leads are untouched unless named in returnContactIds, and that nothing is sent to anyone. Since there is no output schema, the closing sentence about linked contacts, lead status and parked state is also genuinely informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the body is long and drifts into lead-parking mechanics that belong to create_task/update_task/delete_task rather than a read-only listing tool. Several sentences could be trimmed without losing anything an agent needs to call list_tasks.

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?

With no output schema, the description usefully tells the agent that each task carries linked contacts and lead status. For a six-parameter read tool this is close to complete, though it says nothing about result size, pagination, or ordering beyond the limit parameter.

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 all six parameters (limit, owner, search, status, contactId, applicationId) are already documented in the schema. The description adds no syntax or format detail beyond what the schema states, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('List CRM tasks') and characterizes what a task is ('work the team owes, like checking payment records, fixing a bug or sending a refund'), which distinguishes it from create_task/update_task/delete_task. It does not explicitly differentiate from the close sibling list_follow_up_tasks, so it stops short of a 5.

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?

Usage is implied by 'Read-only' and the resource framing, but there is no explicit statement of when to call this versus list_follow_up_tasks or list_pulse_items, nor any prerequisite note. An agent must infer the choice from the name alone.

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

All FlowCastle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources