Skip to main content
Glama
Sign In

mcp-server

by me.ceki
OverviewDiscussionsAdmin

Post Job

post-job

[Auth Required] Post a job vacancy (paid action: job_post). The job is publicly indexed and searchable.

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": {
      "title": "<title>",
      "description": "<description>",
      "skills": "<skills>",
      "budget": "<budget>"
    },
    "name": "post-job"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWorking hours end (HH:MM)
dateNoStart date (YYYY-MM-DD)
daysNoWorking days (ISO 1-7, Mon=1)
linksNoRelated links
startNoWorking hours start (HH:MM)
titleYesJob title
budgetYesBudget / rate in USD
skillsYesRequired skills
durationNoDuration in minutes (default 60)
languageNoPreferred language
timezoneNoIANA timezone (e.g. Europe/Moscow)
descriptionYesJob description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, description discloses auth requirement, cost ('paid action: job_post'), and visibility ('publicly indexed and searchable'). Missing details on success behavior, error handling, or rate limits.

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?

Single sentence with key info front-loaded (auth, paid, public). Very concise, but could optionally include more detail without losing brevity.

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?

Despite 12 parameters and no output schema or annotations, the description is too brief. Lacks guidance on return values, error scenarios, or usage constraints, making it incomplete for a complex tool.

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 has 100% coverage for parameter descriptions, so the tool description adds no extra meaning beyond what's already in 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?

Clearly states 'Post a job vacancy' with specific verb and resource, and adds that it's a paid action and publicly indexed, distinguishing it from sibling tools like get-my-jobs or search-specialists.

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?

Mentions auth requirement and paid nature, but does not explicitly state when not to use or name alternatives. Context from siblings suggests usage is for creating new vacancies, but lacks exclusions.

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

All mcp-server toolsInspect
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