Skip to main content
Glama
Sign In
jobber-mcp

jobber-mcp

by BuildMinimal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get client details

get_client_details

Retrieves a Jobber client's full profile by client_id, including contact details, balance, member-since, recent jobs, and invoices; use search_jobs to find the client_id by name.

Instructions

Full profile for one client by Jobber client_id: name, email/phone, outstanding balance, member-since, recent jobs and recent invoices. Find the client_id first via search_jobs (results include client ids) when you only know the name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>"
    },
    "name": "get_client_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYesJobber client ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the returned data shape, which is genuinely useful, but says nothing about permissions/auth needs, rate limits, or how 'recent' is bounded for jobs and invoices.

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 tight sentences, front-loaded with the purpose and return contents followed by the prerequisite. No filler, every clause earns its place.

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 no output schema, the description correctly enumerates the return fields, so an agent knows what it gets back. The only gap is the vague 'recent jobs and recent invoices', which leaves the time window or count unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, so the baseline is 3; the description goes beyond the schema by explaining how to obtain the client_id via search_jobs, which is practical guidance the schema field itself does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full profile for one client') and enumerates exactly what the profile contains: name, contact info, balance, member-since, recent jobs and invoices. This is clearly distinguishable from siblings like search_jobs or get_unpaid_invoices.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite and workflow: find the client_id via search_jobs when you only know the name. It names the right alternative for name-based lookup, though it stops short of stating when NOT to use this tool (e.g., bulk retrieval).

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

Deploy Server

Other Tools