Skip to main content
Glama
alexherbaly

upservice-mcp

by alexherbaly

upservice_list_tasks

Read-onlyIdempotent

List and search tasks using filters for kind, project, author, responsible, date ranges, and tags.

Instructions

List/search tasks with optional filters for kind, project, author, responsible, date ranges, and tags.

CONFIRMED LIMITATION (verified against the live API, not just the OpenAPI spec): this endpoint has no status/status_in/is_completed/completed/query filter. Passing any of those as extra query params is silently ignored server-side (no error, no effect on results) — status filtering must be done client-side on the returned status field. There is no workaround on the Upservice API today; this has been reported to Upservice as a feature request. Until it lands, narrow results with date_end_gte/date_end_lte (due-date range) plus project/author/responsible BEFORE paginating and filtering by status client-side — e.g. for "open overdue tasks", pass date_end_lte=<now, ISO 8601> together with project/responsible to get a small candidate set, then drop any whose status is completed/cancelled/rejected/deleted. Do not call this with only author (or no filters) and try to page through everything — accounts can have 100k+ tasks and completed_at/date filters are the only server-side way to keep that bounded.

Args: params (ListTasksInput): limit, offset, kind, project, author, responsible, created_at_gte/lte, completed_at_gte/lte, date_start_gte/lte, date_end_gte/lte, tags_ids, tags_condition (all optional except pagination defaults)

Returns: str: JSON list of tasks matching the filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses that certain query parameters are silently ignored (status, status_in, etc.), which is beyond the annotations. Also confirms the endpoint behavior and provides a workaround. Aligns with annotations (readOnlyHint, etc.).

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?

Well-structured with a clear overview, specific limitation block, and usage advice. Despite length, every sentence adds value. Slightly verbose but appropriately so for the complexity.

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 complexity (many optional filters, pagination) and presence of output schema, the description is thoroughly complete. It covers limitations, optimization strategies, and return format, with no obvious gaps.

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

Parameters4/5

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

Schema description coverage is high (100% based on provided schema), so baseline is 3. The description adds value by clarifying the limitation on status filters and recommended usage patterns, going beyond the schema descriptions.

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 starts with 'List/search tasks with optional filters...' clearly stating the verb and resource. It distinguishes from sibling tools like upservice_get_task and other list tools by focusing on listing tasks with filters.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool vs alternatives, including a detailed limitation on status filters, a concrete example for 'open overdue tasks', and warnings against inefficient calls (e.g., with only author). Includes specific recommendations for parameter usage.

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/alexherbaly/upservice-mcp'

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