Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy

autotask_search_billing_items

Search for approved and posted billable billing items in Autotask using filters like date range, ticket, company, invoice, project, contract, and invoiced status. Returns paginated results.

Instructions

Search for billing items in Autotask. Billing items represent approved and posted billable items from the "Approve and Post" workflow. Returns 25 results per page by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
dateToNoFilter billing items with itemDate on or before this date (ISO format)
dateFromNoFilter billing items with itemDate on or after this date (ISO format, e.g. 2026-01-01)
pageSizeNoMax 500
ticketIdNoFilter by ticket ID
companyIdNoFilter by company ID
invoiceIdNoFilter by invoice ID
projectIdNoFilter by project ID
contractIdNoFilter by contract ID
isInvoicedNoIf true, only return billing items that have been attached to an invoice (invoiceID is set). If false, only return items that have not yet been invoiced. Answers "what has and hasn't been invoiced yet".
postedAfterNoFilter items posted on or after this date (ISO format, e.g. 2026-01-01)
postedBeforeNoFilter items posted on or before this date (ISO format)
Behavior3/5

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

With no annotations, the description partially carries the burden. It mentions the default page size (25 results per page), implying a read operation. However, it does not explicitly state that the tool is read-only or disclose any potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. Front-loaded with purpose, followed by definition and default behavior. Structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters with high schema coverage and no output schema, the description provides essential context (definition of billing items, default pagination). It covers the key aspects for a search tool, but could be more complete by confirming read-only nature.

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 description coverage is 92%, so most parameters already have descriptions. The tool description adds only the default page size context, which is implied by pageSize. No additional parameter semantics beyond the schema.

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?

The description clearly states the tool searches for billing items and defines them as 'approved and posted billable items from the 'Approve and Post' workflow.' It distinguishes from siblings by name and context, but does not explicitly differentiate from other search tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites or conditions for use.

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/ThatDayneGuy/autotask-mcp'

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