Skip to main content
Glama

find_billing_work

Find the projects, tasks and subtasks in your organization where time can be tracked. Pass a name fragment as query to search customer, project, task and subtask names at once: every matching subtask comes back in matches with its full path (customer > project > task > subtask) and its subtask_id. Use this to locate where to record work. Returns ids and names only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional case-insensitive name fragment. It matches customer, project, task and subtask names: `projects` lists the projects whose own name or customer's name matches, and `matches` lists every subtask whose own name or task's name matches, with its full path and subtask_id. With project_id, it filters that project's tasks and returns that project's matching subtasks in `matches`.
project_idNoOptional project id to drill into. When supplied, returns that project's tasks and subtasks.
max_resultsNoOptional maximum number of rows to return (1-50, default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional case-insensitive name fragment to filter projects (or tasks when project_id is supplied)."New value: +"Optional case-insensitive name fragment. It matches customer, project, task and subtask names: `projects` lists the projects whose own name or customer's name matches, and `matches` lists every subtask whose own name or task's name matches, with its full path and subtask_id. With project_id, it filters that project's tasks and returns that project's matching subtasks in `matches`."
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources