Skip to main content
Glama

Find AI jobs

find_ai_jobs
Read-onlyIdempotent

Open roles at AI companies, searchable by keyword, company, function (Engineering, Product, Sales, AI & Data, ...) and place (city, country or Remote).

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

Input Schema

NameRequiredDescriptionDefault
roleNoFunction, e.g. Engineering.
limitNoResults to return, 1 to 25.
placeNoCity, country or Remote.
queryNo
cursorNoPass next_cursor from the previous result to get the next page.
companyNoCompany slug or exact name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the facet set and that place accepts 'Remote', but says nothing about result shape, pagination beyond the schema's cursor, or ordering.

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?

A single front-loaded sentence naming the resource first, then the search dimensions. No filler, no repetition of schema or annotation content.

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?

With no output schema, the description should hint at what a result contains, but it only says 'open roles' without describing fields (title, company, location, link). Pagination and limits are covered by the schema, so the remaining gap is the return shape.

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 already high (83%), so a 3 is the baseline. The description goes beyond it by supplying example function values (Engineering, Product, Sales, AI & Data) where the schema offers only one example and no enum, and by clarifying that place accepts a city, country, or the literal 'Remote'.

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 resource (open roles at AI companies) and enumerates the searchable facets, so an agent can tell it apart from search_ai_companies or get_company. It lacks an explicit contrast with those siblings, but the resource noun is unambiguous.

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?

Usage is implied by 'searchable by keyword, company, function and place' — an agent can infer this is the tool for locating job listings. However, no when-to-use/when-not guidance or alternatives are named, so an agent must infer the routing itself.

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