Skip to main content
Glama

Search Jobs

search_jobs
Read-onlyIdempotent

Search jobs using flexible filters like status, customer, date range, address, and more. Paginated results sorted by start date descending.

Instructions

Search for jobs with flexible filters. Supports filtering by status, customer name, date range, address, phone, email, category, and more. Returns paginated results sorted by most recent first by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by job status. Comma-separated for multiple (e.g., 'Open,Scheduled'). Common statuses: Open, Scheduled, Dispatched, In Progress, Completed, Cancelled.
sub_statusNoFilter by sub-status (exact match). May not be supported by all accounts.
customer_nameNoFilter by customer name (partial match).
start_date_gteNoJobs starting on or after this date (YYYY-MM-DD).
start_date_lteNoJobs starting on or before this date (YYYY-MM-DD).
end_date_gteNoJobs ending on or after this date (YYYY-MM-DD).
end_date_lteNoJobs ending on or before this date (YYYY-MM-DD).
addressNoFilter by job address (partial match).
cityNoFilter by city (exact match).
zip_codeNoFilter by zip/postal code (exact match).
phoneNoFilter by phone number (partial match).
emailNoFilter by email address (exact match).
categoryNoFilter by job category. Comma-separated for multiple.
sourceNoFilter by lead source. Comma-separated for multiple.
numberNoFilter by job number (partial match).
sortNoSort results. Prefix with '-' for descending. Examples: '-start_date', 'customer_name', '-created_at'. Default: '-start_date'.
pageNoPage number (default: 1).
per_pageNoResults per page (default: 20, max: 50).
Behavior4/5

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

Annotations already indicate a safe read operation. The description adds behavioral context about pagination and default sort order, which is beyond the annotations.

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 effectively convey the purpose and key features. The information is front-loaded and every sentence earns its place.

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?

The description covers main functionality and pagination but does not describe the response structure or error handling. Given the number of parameters and lack of output schema, it could be more complete.

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 coverage is 100%, so the schema already describes each parameter. The description provides a high-level summary but does not add new meaning beyond grouping the filters.

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 jobs with flexible filters, listing specific filter fields. However, it does not explicitly differentiate from sibling tools like get_customer_jobs or get_todays_jobs.

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 is provided on when to use this tool versus alternatives. It does not mention scenarios where a sibling tool would be more appropriate.

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/commair-tools/mcp-servicefusion-public'

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