Crawlora MCP

tesla_jobs_list

Read-only

Search and paginate Tesla's public careers job dataset with the supplied filters. Use tesla_jobs_job to retrieve one job's details after finding its listing.

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": "tesla_jobs_list"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, 1-based
`query`	No	Filter by title or department, case-insensitive substring match
`location`	No	Filter by location, case-insensitive substring match
`page_size`	No	Results per page, up to 100

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / location / description
```
Added value: +"Filter by location, case-insensitive substring match"
```
- addedInput schema / properties / page / description
```
Added value: +"Page number, 1-based"
```
- addedInput schema / properties / page_size / description
```
Added value: +"Results per page, up to 100"
```
- addedInput schema / properties / query / description
```
Added value: +"Filter by title or department, case-insensitive substring match"
```
First observedOct 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds the pagination trait and that the dataset is public, but says nothing about result caps, rate limits, or freshness beyond what annotations and the output schema provide.

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 with no waste: the purpose and pagination behavior come first, and the routing hint to tesla_jobs_job follows. Every sentence 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?

An output schema exists, so return values need not be described. The description covers purpose, pagination, and sibling routing adequately; only minor behavioral detail (result limits, empty-query behavior) is absent.

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 page, query, location, and page_size are fully documented in the schema. The description references 'the supplied filters' generically without adding syntax, match semantics, or defaults beyond the schema. Baseline 3 applies.

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 pair (search and paginate) plus the exact resource (Tesla's public careers job dataset), and explicitly distinguishes itself from the sibling tesla_jobs_job. An agent can tell this is the list/search entry point without opening the schema.

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?

Names the alternative tool and the condition that selects it: use tesla_jobs_job to get one job's details after finding its listing. Clear workflow context, though it doesn't spell out when-not to use this tool (e.g., still valid with no filters).

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.