Teamtailor Ops Control Plane

by app.vercel.ats-ops-control-plane-gateway

create_job_application

Create a Teamtailor job application.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Set true to run this live change. Ignored when dry_run=true.
`dry_run`	No	Preview the action without sending it.
`body_json`	No	JSON request body for documented write operations.
`query_json`	No	Additional documented query parameters, including bracketed filter keys.
`path_params`	No	Values for path placeholders such as {id} in a write operation.
`headers_json`	No	Additional request headers for endpoints that require vendor-specific headers.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 7, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Set true to run this live change. Ignored when dry_run=true.",
+  "type": "boolean"
+}

First observedJun 5, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, and the description merely says 'Create a Teamtailor job application.' It does not disclose side effects, required confirm/dry_run semantics, authentication needs, or expected return behavior, offering no behavioral context beyond the tool name.

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?

The description is a single, front-loaded sentence with no filler, making it concise. However, it is under-specified; adding a second sentence about required input or usage would improve value without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, this one-sentence description is insufficient for a mutation tool with six generic parameters. An agent cannot determine the required payload structure, confirmation flow, or expected outcome, making the description incomplete for the tool's complexity.

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 has 100% description coverage for all six parameters, but those descriptions are generic boilerplate (e.g., 'JSON request body for documented write operations'). The tool description adds no job-application-specific parameter guidance, so the baseline 3 applies due to full schema coverage.

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?

The description uses the specific verb 'Create' with the resource 'a Teamtailor job application', making the tool's purpose clear. It is distinguishable from sibling tools like create_candidate or create_job, though it does not explicitly differentiate itself.

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?

There is no guidance on when to use this tool versus alternatives such as create_candidate, create_job, or update_job_application. The description only states the action and offers no context for selection.

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

All Teamtailor Ops Control Plane tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0

Disambiguation4/5

Most tools have clearly distinct purposes due to specific resource names and detailed descriptions. However, the large number of similar get/list pairs (e.g., get_activity, get_answer) could cause an agent to misselect without careful reading, slightly reducing clarity.

Naming Consistency5/5

The naming follows a strict and predictable verb_noun pattern (list_/get_/create_/update_) using snake_case throughout. The only outlier is 'api_request', but it is a generic tool and does not break the overall pattern.

Tool Count3/5

With 62 tools, the set is large but arguably justified by the breadth of the Teamtailor domain (candidates, jobs, applications, interviews, notes, etc.). Still, it exceeds the typical 3-15 range for high coherence, making navigation heavy for agents.

Completeness3/5

The tool set provides comprehensive read access (get/list) for most entities, but lacks delete operations entirely and has limited update coverage (only candidate, job, job_application). The 'api_request' tool can compensate, but the surface has notable gaps in mutation capabilities.

Resources

Need Help?