Semata

Parse job description

parse_job_description

Read-only

Turn a job description into a role draft for the user to review before creating the role. Pass either the pasted text or a public job-posting URL, not both; Semata fetches the URL itself with its safe fetcher. Nothing is saved. After review, use create_role_from_jd with the original text or URL to create the role and retain its full original description. create_role accepts a draft but has no original source. Requires OAuth or a scoped token.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "parse_job_description"
  }
}

Input Schema

Name	Required	Description
`url`	No	A public job-posting URL starting with https://.
`text`	No	The full job description text.
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover the read-only/destructive profile, and the description still adds real context beyond them: 'Nothing is saved', URL fetching is done server-side by a safe fetcher (so the agent should not fetch first), and OAuth or scoped-token auth is required. The only gap is the shape of the returned draft, which matters because there is no output schema.

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?

Purpose is front-loaded in the first sentence, followed by input rules, safety, and next-step routing in descending priority. Every sentence carries distinct information with no restatement of the title or schema.

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?

Auth, side-effect status, input exclusivity, and follow-up routing are all covered, which is strong for a tool with no output schema. The one omission is any hint about what the draft contains or how parse failures surface, leaving the agent to discover the return shape by calling it.

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% so the baseline is 3, but the description adds the mutual-exclusivity rule between text and url that the schema does not encode (neither is required individually). It also clarifies the URL is fetched by the service rather than by the caller.

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 concrete verb and resource ('Turn a job description into a role draft') plus the intermediate review step. It explicitly distinguishes itself from both create_role_from_jd and create_role, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit branching rules: pass either text or URL, not both, and use create_role_from_jd afterwards if the role is confirmed. It also names the wrong sibling and why it is wrong ('create_role accepts a draft but has no original source'), which is exactly the routing information an agent needs.

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

All Semata 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.

Resources

Need Help?