Service Fusion MCP by usefulapi

List jobs

servicefusion_list_jobs

Read-only

List jobs (work orders). Filter by status, number, PO or invoice number, customer, contact, address, phone, email, category, source and start/end/updated/closed dates. Add expand (techs_assigned, services, products, payments, invoices, visits, notes, ...) for detail. GET /jobs.

Input Schema

Name	Required	Description
`city`	No	City (exact match).
`page`	No	Page number, from 1 (default 1). Pass the previous reply's next_page.
`sort`	No	Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).
`email`	No	Email (exact match).
`phone`	No	Phone (partial match).
`expand`	No	Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, labor_charges, expenses, payments, invoices, signatures, printable_work_order, visits, visits.techs_assigned.
`fields`	No	Only return these fields, comma-separated (for example id,customer_name). Default: all.
`number`	No	Job number (partial match).
`source`	No	Sources, comma-separated (exact match).
`status`	No	Job status names, comma-separated (exact match; see servicefusion_list_job_statuses).
`address`	No	Street address (partial match).
`category`	No	Job categories, comma-separated (exact match).
`per_page`	No	Results per page, 1-50 (default 10).
`zip_code`	No	Postal/ZIP code (exact match).
`closed_to`	No	Closed at or before (RFC 3339 date-time with timezone).
`po_number`	No	PO number (partial match).
`updated_to`	No	Updated at or before (RFC 3339 date-time with timezone).
`closed_from`	No	Closed at or after (RFC 3339 date-time with timezone).
`end_date_to`	No	Job end date on or before, yyyy-mm-dd.
`updated_from`	No	Updated at or after (RFC 3339 date-time with timezone).
`customer_name`	No	Customer name (partial match).
`end_date_from`	No	Job end date on or after, yyyy-mm-dd.
`start_date_to`	No	Job start date on or before, yyyy-mm-dd.
`invoice_number`	No	Invoice number (partial match).
`start_date_from`	No	Job start date on or after, yyyy-mm-dd.
`contact_last_name`	No	Contact last name (partial match).
`contact_first_name`	No	Contact first name (partial match).
`parent_customer_name`	No	Parent customer name (partial match).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful behavior around expand and notes GET /jobs, but does not mention pagination behavior, rate limits, auth needs, or return shape.

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 and compact, with filters and expand grouped efficiently. The trailing 'GET /jobs' is mildly redundant given readOnlyHint but not harmful.

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?

Complete enough for a paginated list tool: it explains filters, expand, and endpoint, while the schema covers pagination and field details. Lacking an output schema, it could say more about returned job records, but that is a minor gap.

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 100%, so all 28 parameters are already documented. The description groups filters and mentions expand examples, but adds little semantic detail beyond what the schema provides.

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 clear verb and resource: 'List jobs (work orders).' It is easy to distinguish from get_job or list_customers, though it does not explicitly name sibling alternatives.

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?

The filter list implies how to use the tool for searching jobs, and expand is described for detail. However, there is no explicit guidance on when to use this versus get_job or when to consult list_job_statuses/list_sources.

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

All Service Fusion MCP by usefulapi 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 jobs

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources