Skip to main content
Glama

list_tasks

List tasks of a project. Filter by epicId, status, standalone (tasks not linked to any epic), assignee, surface, or label. If the user is working inside a VSCode workspace and /.bilg/bilg.config.json has a "surface", pass it as surface unless the user asks for the whole project. If the user is working inside a VSCode workspace and a <workspace>/.bilg/bilg.config.json exists, prefer that file's projectName over the API key's default project.

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
labelNoLabel (comma-separated for several): only items carrying one of them.
epicIdNoOnly tasks of this epic
statusNo
surfaceNoSurface name or id (comma-separated for several); "all" = the whole project. Shows items on that surface plus project-wide items. Defaults to the connection's surface, if any.
assigneeNo"me", "unassigned", "all" (default), a person's name, the email shown for members without a name, or id
standaloneNoIf true, only tasks not linked to an epic
projectNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / label
      Added value: +{
      +  "description": "Label (comma-separated for several): only items carrying one of them.",
      +  "type": "string"
      +}
    • addedInput schema / properties / surface
      Added value: +{
      +  "description": "Surface name or id (comma-separated for several); \"all\" = the whole project. Shows items on that surface plus project-wide items. Defaults to the connection's surface, if any.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses useful defaults (surface falls back to the connection's surface, assignee defaults to 'all', 'all' surface means whole project), but says nothing about authorization, result limits/pagination, or ordering. For a read-only list that is a reasonable but incomplete disclosure.

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?

Front-loaded with purpose and filters before the workspace caveats. The two VSCode sentences are somewhat long and overlapping, but each carries non-obvious routing logic rather than filler.

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?

Seven parameters, no output schema, and no annotations mean the description should say more about what is returned (task shape, paging, ordering). It covers filtering and workspace precedence well but leaves the response behavior entirely undocumented.

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?

The description enumerates all filter dimensions and, critically, explains the config-file-driven behavior for `surface` and `projectName` that the schema does not. With schema coverage at 71%, this adds real meaning beyond the structured fields, though it doesn't clarify combined-filter semantics.

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 tasks of a project') and immediately enumerates the filter dimensions, making it distinguishable from get_task and list_epics. It does not explicitly name a sibling, but the singular/plural and read semantics are clear.

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

Usage Guidelines4/5

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

Gives concrete conditional guidance: pass the workspace config's surface unless the user wants the whole project, and prefer config projectName over the API key default. It does not cover when to use this versus other list tools, but the workspace-routing rules are genuinely actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources