Skip to main content
Glama

Request Outcome-Based Employer Pilot Review

start_checkout

Returns a non-charging owner-review request template for the Verified Interview Pilot only. It creates no request, program, candidate action, invoice, or charge. Employer identity, exact-role authority, and acknowledgement of the capped 30-day terms are required before a separate review request may be submitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoVerified Interview Pilot employer company.
product_idNoProduct ID from list_products.
work_emailNoVerified Interview Pilot work email. Included only in the returned review-request template; this MCP call does not submit it.
employer_nameNoVerified Interview Pilot employer contact name. Included only in the returned review-request template; this MCP call does not submit it.
pilot_role_referenceNoPublic job URL, requisition ID, or exact role reference for the pilot.
pilot_authority_assertedNoTrue only after the principal explicitly authorizes requesting owner review for this exact employer and role.
pilot_terms_acknowledgedNoTrue only after the employer principal acknowledges the canonical 30-day, $99-per-mutually-confirmed-interview, three-interview/$297-cap terms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / buyer_email
      Removed value: -{
      -  "description": "Required by POST /api/v1/checkout for sponsored listing highlights. For the AI Market Demand Pack, MCP never creates a Stripe session from buyer_email alone; it returns a human review URL plus the company-authenticated checkout handoff. A registered company's agent must use that handoff with explicit principal authorization.",
      -  "type": "string"
      -}
    • removedInput schema / properties / demand_category
      Removed value: -{
      -  "description": "Optional fixed demand category copied from provider_market_signal checkout.arguments; raw queries are not accepted.",
      -  "enum": [
      -    "agent_systems",
      -    "ai_infrastructure",
      -    "llm_applications",
      -    "computer_vision",
      -    "nlp_and_speech",
      -    "robotics_autonomy",
      -    "data_engineering",
      -    "ai_security_safety",
      -    "ai_research",
      -    "ml_engineering",
      -    "ai_product_go_to_market",
      -    "other"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / job_id
      Removed value: -{
      -  "description": "Required for aidevboard_promote_listing.",
      -  "type": "string"
      -}
    • removedInput schema / properties / payment_mode
      Removed value: -{
      -  "description": "Payment mode. stripe_checkout is the default; stripe_spt is supported for sponsored-highlight checkout when the HTTP caller supplies shared_payment_granted_token to /api/v1/checkout.",
      -  "enum": [
      -    "stripe_checkout",
      -    "stripe_link",
      -    "link",
      -    "stripe_spt"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / sku
      Removed value: -{
      -  "description": "Dossier SKU alias: baseline, pitch, or pitch10.",
      -  "type": "string"
      -}
    • removedInput schema / properties / source_tool
      Removed value: -{
      -  "description": "Optional fixed source from a provider_market_signal checkout.arguments object. Used only to preserve search or match attribution.",
      -  "enum": [
      -    "search_jobs",
      -    "match_jobs"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / visible_job_results
      Removed value: -{
      -  "description": "Optional bounded visible-result count copied from provider_market_signal checkout.arguments.",
      -  "maximum": 25,
      -  "minimum": 1,
      -  "type": "integer"
      -}
  2. Changed1 schema field changed
    • changedInput schema / properties / buyer_email / description
      Previous value: -"Required by POST /api/v1/checkout for sponsored listing highlights and direct agentic AI Market Demand Pack Stripe sessions. Without it, the Market Demand Pack returns a side-effect-free human review URL."New value: +"Required by POST /api/v1/checkout for sponsored listing highlights. For the AI Market Demand Pack, MCP never creates a Stripe session from buyer_email alone; it returns a human review URL plus the company-authenticated checkout handoff. A registered company's agent must use that handoff with explicit principal authorization."
  3. Changed3 schema fields changed
    • addedInput schema / properties / demand_category
      Added value: +{
      +  "description": "Optional fixed demand category copied from provider_market_signal checkout.arguments; raw queries are not accepted.",
      +  "enum": [
      +    "agent_systems",
      +    "ai_infrastructure",
      +    "llm_applications",
      +    "computer_vision",
      +    "nlp_and_speech",
      +    "robotics_autonomy",
      +    "data_engineering",
      +    "ai_security_safety",
      +    "ai_research",
      +    "ml_engineering",
      +    "ai_product_go_to_market",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / source_tool
      Added value: +{
      +  "description": "Optional fixed source from a provider_market_signal checkout.arguments object. Used only to preserve search or match attribution.",
      +  "enum": [
      +    "search_jobs",
      +    "match_jobs"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / visible_job_results
      Added value: +{
      +  "description": "Optional bounded visible-result count copied from provider_market_signal checkout.arguments.",
      +  "maximum": 25,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / buyer_email / description
      Previous value: -"Required by POST /api/v1/checkout for sponsored listing highlights. Blocks anonymous probes from creating pending Stripe sessions."New value: +"Required by POST /api/v1/checkout for sponsored listing highlights and direct agentic AI Market Demand Pack Stripe sessions. Without it, the Market Demand Pack returns a side-effect-free human review URL."
  5. Changed6 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Verified Interview Pilot employer company.",
      +  "type": "string"
      +}
    • addedInput schema / properties / employer_name
      Added value: +{
      +  "description": "Verified Interview Pilot employer contact name. Included only in the returned review-request template; this MCP call does not submit it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / pilot_authority_asserted
      Added value: +{
      +  "description": "True only after the principal explicitly authorizes requesting owner review for this exact employer and role.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / pilot_role_reference
      Added value: +{
      +  "description": "Public job URL, requisition ID, or exact role reference for the pilot.",
      +  "type": "string"
      +}
    • addedInput schema / properties / pilot_terms_acknowledged
      Added value: +{
      +  "description": "True only after the employer principal acknowledges the canonical 30-day, $99-per-mutually-confirmed-interview, three-interview/$297-cap terms.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / work_email
      Added value: +{
      +  "description": "Verified Interview Pilot work email. Included only in the returned review-request template; this MCP call does not submit it.",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / buyer_email / description
      Previous value: -"Required by POST /api/v1/checkout for promoted listings. Blocks anonymous probes from creating pending Stripe sessions."New value: +"Required by POST /api/v1/checkout for sponsored listing highlights. Blocks anonymous probes from creating pending Stripe sessions."
    • changedInput schema / properties / payment_mode / description
      Previous value: -"Payment mode. stripe_checkout is the default; stripe_spt is supported for promoted-listing checkout when the HTTP caller supplies shared_payment_granted_token to /api/v1/checkout."New value: +"Payment mode. stripe_checkout is the default; stripe_spt is supported for sponsored-highlight checkout when the HTTP caller supplies shared_payment_granted_token to /api/v1/checkout."
  7. Changed1 schema field changed
    • changedInput schema / properties / buyer_email / description
      Previous value: -"Optional buyer email to prefill Stripe Checkout."New value: +"Required by POST /api/v1/checkout for promoted listings. Blocks anonymous probes from creating pending Stripe sessions."
  8. Changed2 schema fields changed
    • changedInput schema / properties / payment_mode / description
      Previous value: -"Payment mode. stripe_checkout is the default supported mode."New value: +"Payment mode. stripe_checkout is the default; stripe_spt is supported for promoted-listing checkout when the HTTP caller supplies shared_payment_granted_token to /api/v1/checkout."
    • changedInput schema / properties / payment_mode / enum
      Previous value: -[
      -  "stripe_checkout",
      -  "stripe_link",
      -  "link"
      -]New value: +[
      +  "stripe_checkout",
      +  "stripe_link",
      +  "link",
      +  "stripe_spt"
      +]
  9. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly describes the tool as non-charging, states that it creates no request/program/candidate action/invoice/charge, and clarifies that fields like work_email and employer_name are only included in the returned template, not submitted. This is excellent transparency beyond the 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?

The description is two sentences and front-loaded with the primary action ('Returns a non-charging owner-review request template') followed by a concise list of exclusions and prerequisites. Every clause earns its place with no redundancy.

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

Completeness5/5

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

For a 7-parameter tool with no output schema and no annotations, this description is remarkably complete. It tells the agent what is returned, what is not created, and the required preconditions before a subsequent review request can be submitted. Combined with the detailed schema, there are no significant contextual gaps.

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?

Input schema coverage is 100%, so the schema already provides complete parameter semantics. The description's mention of required identity, authority, and terms acknowledgment loosely maps to parameters but adds little new information beyond emphasizing prerequisites. Baseline 3 is appropriate.

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?

The description states a specific action: it returns a non-charging owner-review request template for the Verified Interview Pilot only. It also clarifies what it does not do (creates no request, program, candidate action, invoice, or charge), which sharply distinguishes it from sibling tools like apply_to_job or quote_product.

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?

The description provides clear context: the tool is for the Verified Interview Pilot only and is a prerequisite step before a separate review request can be submitted. It states required conditions (employer identity, exact-role authority, acknowledgment of capped terms) but does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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