Onplana

list_projects

Read-onlyIdempotent

List the projects in the user's Onplana workspace, with status and dates. Fits "what projects do I have", "how are my projects doing" and finding the project a request refers to. To FIND A PROJECT BY NAME, pass search (case-insensitive substring on the name) rather than listing everything and matching client-side, which silently misses projects past limit in orgs with more projects than one page. Also filters by status and customFields. Returns up to limit projects ordered by most recently updated; total is how many MATCH (not just this page), and when truncated is true pass nextCursor back as cursor for the next page. Non-admin users only see projects they own or are a member of. On a first connect to a new org, whoami + describe_capabilities + describe_schema ground caller identity, available tools and entity shapes, which the list_* tools all read against. Each project carries autoSchedule; false means edits and links there move no other task. And parentDatesFromSubtasks, the default for a task with subtasks, and retainedLogic, whether a late predecessor pushes a started task. Archived projects are hidden unless includeArchived is true; an archived project carries archivedAt and is read-only until it is unarchived.

Input Schema

Name	Required	Description
`limit`	No	Max projects to return per page (1-50). Default 20. Use cursor to page further.
`cursor`	No	Last-id pagination cursor from a prior call's nextCursor.
`search`	No	Case-insensitive substring match on the project name. Use this to look a project up by name instead of paging the whole org.
`status`	No	Optional: only return projects with this status.
`customFields`	No	Filter by custom-field value(s); multiple entries are ANDed. Each entry is { fieldId, op, value? }. Ops must be valid for the field type , numeric (NUMBER/CURRENCY/RATING): eq/gt/gte/lt/lte/isNotEmpty; DATE: eq/before/after/isNotEmpty; text/DROPDOWN: eq/contains/isNotEmpty; MULTI_SELECT: contains/isNotEmpty; CHECKBOX: isChecked/isUnchecked (unchecked includes never set). Omit value for isNotEmpty, isChecked and isUnchecked. No neq / isEmpty. Get field ids from list_custom_field_defs.
`includeArchived`	No	Also list archived (read-only) projects. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / customFields / description

Previous value: -"Filter by custom-field value(s); multiple entries are ANDed. Each entry is { fieldId, op, value? }. Ops must be valid for the field type , numeric (NUMBER/CURRENCY/RATING): eq/gt/gte/lt/lte/isNotEmpty; DATE: eq/before/after/isNotEmpty; text/DROPDOWN: eq/contains/isNotEmpty; MULTI_SELECT: contains/isNotEmpty; CHECKBOX: eq/isNotEmpty. Omit value only for isNotEmpty. Inclusion-only in v1 (no neq / isEmpty). Get field ids from list_custom_field_defs."New value: +"Filter by custom-field value(s); multiple entries are ANDed. Each entry is { fieldId, op, value? }. Ops must be valid for the field type , numeric (NUMBER/CURRENCY/RATING): eq/gt/gte/lt/lte/isNotEmpty; DATE: eq/before/after/isNotEmpty; text/DROPDOWN: eq/contains/isNotEmpty; MULTI_SELECT: contains/isNotEmpty; CHECKBOX: isChecked/isUnchecked (unchecked includes never set). Omit value for isNotEmpty, isChecked and isUnchecked. No neq / isEmpty. Get field ids from list_custom_field_defs."

changedInput schema / properties / customFields / items / properties / op / enum

Previous value: -[
-  "eq",
-  "contains",
-  "gt",
-  "gte",
-  "lt",
-  "lte",
-  "before",
-  "after",
-  "isNotEmpty"
-]New value: +[
+  "eq",
+  "contains",
+  "gt",
+  "gte",
+  "lt",
+  "lte",
+  "before",
+  "after",
+  "isNotEmpty",
+  "isChecked",
+  "isUnchecked"
+]

changedInput schema / properties / customFields / items / properties / value / description

Previous value: -"Comparison value; omit for isNotEmpty."New value: +"Comparison value; omit for isNotEmpty, isChecked and isUnchecked."

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Last-id pagination cursor from a prior call's nextCursor.",
+  "type": "string"
+}

addedInput schema / properties / customFields

Added value: +{
+  "description": "Filter by custom-field value(s); multiple entries are ANDed. Each entry is { fieldId, op, value? }. Ops must be valid for the field type , numeric (NUMBER/CURRENCY/RATING): eq/gt/gte/lt/lte/isNotEmpty; DATE: eq/before/after/isNotEmpty; text/DROPDOWN: eq/contains/isNotEmpty; MULTI_SELECT: contains/isNotEmpty; CHECKBOX: eq/isNotEmpty. Omit value only for isNotEmpty. Inclusion-only in v1 (no neq / isEmpty). Get field ids from list_custom_field_defs.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "fieldId": {
+        "description": "CustomFieldDefinition id (scoped to this org + entity).",
+        "type": "string"
+      },
+      "op": {
+        "enum": [
+          "eq",
+          "contains",
+          "gt",
+          "gte",
+          "lt",
+          "lte",
+          "before",
+          "after",
+          "isNotEmpty"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "Comparison value; omit for isNotEmpty.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fieldId",
+      "op"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / includeArchived

Added value: +{
+  "description": "Also list archived (read-only) projects. Default false.",
+  "type": "boolean"
+}

changedInput schema / properties / limit / description

Previous value: -"Max projects to return (1–50). Default 20."New value: +"Max projects to return per page (1-50). Default 20. Use cursor to page further."

addedInput schema / properties / search

Added value: +{
+  "description": "Case-insensitive substring match on the project name. Use this to look a project up by name instead of paging the whole org.",
+  "type": "string"
+}

AddedJun 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond read-only annotations, it discloses non-admin visibility restrictions, archived-project read-only behavior, pagination truncation semantics, total vs page counts, and project-level scheduling flags. These are behavioral details an annotations-only view would not provide.

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?

It is front-loaded with the core purpose and main usage distinction. However, it is dense and includes tangential guidance about bootstrap tools and project scheduling internals that, while useful, make it longer than necessary for selecting this tool.

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?

With no output schema and six optional parameters, the description still covers return ordering, pagination, permissions, archived visibility, and key project fields. It gives enough context for an agent to call and interpret the tool correctly.

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 coverage is 100%, so the schema already documents each parameter. The description adds useful operational meaning around `search` preventing missed projects past `limit`, and links `total`/`truncated` to cursor paging, but it largely echoes schema details for `customFields` and filtering.

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?

It states a specific verb and resource ('List the projects in the user's Onplana workspace') and adds the returned fields ('status and dates'). It also distinguishes the tool from name lookup by directing callers to `search`, making the intended operation clear even among many list_* siblings.

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?

The description gives explicit use cases ('what projects do I have', 'how are my projects doing', finding a project) and explicitly routes name lookup to `search` rather than client-side matching. It also documents filter use, archived inclusion, pagination, and first-connect grounding with whoami/describe_capabilities/describe_schema.

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

All Onplana tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

list_projects

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources