Skip to main content
Glama

Search Jobs Tool

search-jobs
Read-only

Searches the authenticated workspace jobs using safe summary fields only; it does not return service addresses, notes, or amounts. Use to search jobs in the connected business. Returns query, count, jobs, scope.

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": "search-jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return.
queryNoCustomer name, email, phone, or job title.
statusNoOptional job status filter.
customer_idNoRestrict results to one customer ID.
location_idNoRestrict results to one business location ID.
scheduled_toNoInclusive scheduled date, YYYY-MM-DD.
scheduled_fromNoInclusive scheduled date, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
jobsYesBounded jobs records returned by this tool.
countYesCount for the returned result.
queryYesQuery used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "jobs": {
      +      "description": "Bounded jobs records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "description": "Query used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "count",
      +    "jobs",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description's genuinely additive content is the negative disclosure that service addresses, notes, and amounts are omitted, which tells the agent when it must escalate to get-job. However, the "returns query, count, jobs, scope" sentence merely restates the output schema and adds no behavioral context.

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?

Two sentences, front-loaded with the scope restriction and the excluded-field warning, with no filler. The trailing enumeration of return fields is largely redundant given the output schema and is the one expendable element.

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?

With annotations covering safety, a fully described seven-parameter schema, and an output schema handling return structure, the description supplies what is missing: the sensitive-field exclusion. Only the lack of sibling routing guidance keeps it from being fully complete for a search tool in a dense catalog.

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 seven parameters (limit, query, status, customer_id, location_id, scheduled_from/to) are already documented with types, bounds, and formats. The description adds no interpretation of these beyond the general "search jobs" framing, so the baseline of 3 applies.

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 specific verb and resource ("Searches the authenticated workspace jobs") plus an explicit data-scope constraint ("safe summary fields only"), which distinguishes it from the get-job siblings that return full records. It stops short of naming any sibling explicitly, so differentiation relies on the agent inferring search-vs-get semantics.

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?

"Use to search jobs in the connected business" is only an implied-usage statement; it gives no condition for choosing this over jobs-today, get-job, or search-customers. There are no exclusions or prerequisites stated, leaving the routing decision to inference from the tool names.

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