Groundbase

List tasks

tasks_list

Read-onlyIdempotent

List tasks, events and meetings (default: open, every kind), or id for one. Google Calendar events show as kind event. color_id: 1 Lavender, 2 Sage, 3 Grape, 4 Flamingo, 5 Banana, 6 Tangerine, 7 Peacock, 8 Graphite, 9 Blueberry, 10 Basil, 11 Tomato; null default. from+to adds repeating dates (is_virtual: no item of its own; root_id = the series).

Input Schema

Name	Required	Description
`id`	No	Task id. Returns that one item.
`to`	No	ISO 8601; due on/before.
`from`	No	ISO 8601; due on/after.
`kind`	No
`limit`	No
`dealId`	No
`offset`	No
`status`	No	Default open.
`contactId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026
- addedInput schema / properties / status / description
```
Added value: +"Default open."
```
- changedInput schema / properties / status / enum
```
Previous value: -[
-  "open",
-  "done"
-]New value: +[
+  "open",
+  "done",
+  "all"
+]
```

Changed5 schema fields changedOct 1, 2026

removedInput schema / properties / contactId / description
```
Removed value: -"Limit to a single contact's tasks."
```
removedInput schema / properties / dealId / description
```
Removed value: -"Limit to a single deal."
```

changedInput schema / properties / from / description

Previous value: -"ISO 8601 — only items due on/after this date."New value: +"ISO 8601; due on/after."

addedInput schema / properties / id

Added value: +{
+  "description": "Task id. Returns that one item.",
+  "type": "string"
+}

changedInput schema / properties / to / description

Previous value: -"ISO 8601 — only items due on/before this date."New value: +"ISO 8601; due on/before."

First observedSep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile needs no restating. The description does add real behavioral context beyond them: Google Calendar events surface as kind=event, and from+to expands recurring items where is_virtual/root_id mark series members.

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?

Single dense paragraph with the primary purpose and defaults front-loaded; the long color_id enumeration is verbose but carries information absent from the schema.

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 9-parameter, zero-required list tool with no output schema, missing pagination (limit/offset) and the relationship-filtering semantics of dealId/contactId are meaningful gaps an agent would have to guess at.

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 coverage is only 44%, and the description compensates for status/kind/from/to plus the color_id legend, but says nothing about limit, offset, dealId, or contactId, leaving half the parameters undocumented in both places.

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 (list) plus the resources covered (tasks, events, meetings) and explicitly notes the single-item mode via `id`, which separates it from tasks_manage.

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?

Gives useful default conditions ('default: open, every kind') and the from+to repeating-date caveat, but never states when to use this versus tasks_manage, meetings_book, or the other list siblings.

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

All Groundbase tools Inspect

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

Need Help?