Skip to main content
Glama
Medina-Digital-A-i

Jobber MCP Connector

by Medina-Digital-A-i
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobber_create_client

Create a client in Jobber with contact and billing details, and receive the new client's ID.

Instructions

Create a new client in Jobber. Returns the created client with their ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoBilling city
emailNoPrimary email address
phoneNoPrimary phone number
streetNoBilling street address
countryNoCountry (default: US)
lastNameYesClient's last name
provinceNoState or province
firstNameYesClient's first name
postalCodeNoZIP or postal code
companyNameNoCompany name (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral transparency burden. It does disclose the core side effect: a new client is created and the created client is returned with an ID. However, it omits other relevant behaviors such as duplicate handling, idempotency, permission requirements, or failure behavior. This is adequate but not thorough.

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?

The description is a single, well-structured sentence with no filler. The primary action is front-loaded, and the return behavior is stated efficiently. Every word 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?

For a create operation with no annotations and no output schema, the description is reasonably complete: it states the action and the core return value. However, it could be more complete by noting required fields behavior, potential duplicate-client risks, or any external constraints. The 100% schema coverage mitigates but does not fully eliminate this 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?

The schema already documents all 10 parameters with descriptions, so the baseline is 3. The tool description adds no additional parameter-level meaning, but none is needed because the schema coverage is complete.

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?

The description clearly states the action ('Create'), the target resource ('a new client'), and the platform ('Jobber'). It also specifies the return value, which unambiguously distinguishes it from sibling tools like jobber_list_clients and jobber_create_job.

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?

The description gives no guidance on when to use this tool versus alternatives. For example, it does not suggest checking existing clients with jobber_list_clients before creating, nor does it mention when a client should be created vs. updated. The usage context is only implied by the tool name and basic action.

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