made.show

Publish a tailored portfolio

publish_tailored_view

Compose a shareable portfolio page for your criteria, rendered in the candidate's own template. Each section is a criterion with the blocks (by kind + id from get_portfolio / match_criteria) that evidence it. You may add a short note per item explaining relevance; notes are labelled as AI-written. You cannot add new content: unknown ids are rejected. The candidate is notified.

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>",
      "sections": "<sections>"
    },
    "name": "publish_tailored_view"
  }
}

Input Schema

Name	Required	Description
`gaps`	No	Criteria with no evidence. Shown honestly on the page.
`title`	Yes	e.g. "Senior Product Designer — Design Systems"
`handle`	No	Handle or full name
`company`	No	The hiring company, shown on the page
`sections`	Yes	One section per criterion

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 11, 2026
- addedInput schema / properties / company / description
```
Added value: +"The hiring company, shown on the page"
```
- addedInput schema / properties / sections / description
```
Added value: +"One section per criterion"
```
- addedInput schema / properties / sections / items / properties / criterion / description
```
Added value: +"The requirement this section answers"
```
- addedInput schema / properties / sections / items / properties / items / description
```
Added value: +"Portfolio blocks that evidence the criterion"
```
- addedInput schema / properties / sections / items / properties / items / items / properties / id / description
```
Added value: +"Block id from get_portfolio or match_criteria"
```
- addedInput schema / properties / sections / items / properties / items / items / properties / kind / description
```
Added value: +"Type of portfolio block"
```
- addedInput schema / properties / sections / items / properties / items / items / properties / note / description
```
Added value: +"Why this block is relevant. Labelled as AI-written"
```
First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare a non-read-only, open-world, non-idempotent write, and the description adds real context beyond them: the candidate is notified (a visible side effect), unknown ids are rejected, notes are attributed as AI-written, and output uses the candidate's own template. The remaining gap is re-publish semantics — with idempotentHint=false, it never says whether a second call creates a duplicate page or replaces the prior one.

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?

Five short sentences, front-loaded with the outcome before the constraints, and every sentence carries a distinct rule (composition, sourcing, notes, rejection, notification). No filler or restatement of the title.

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 never says what the agent gets back — a URL, a page id, or nothing — which matters for a publish action the agent may need to reference later. It also omits what happens when publishing again. Coverage of inputs and side effects is otherwise solid for a 5-parameter nested write.

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 description coverage is 100%, so the schema already explains title, handle, company, gaps, sections, kind, id, and note. The description reinforces the id-sourcing rule and the AI-labelling of notes but adds no meaning beyond what the schema states. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb and resource: 'Compose a shareable portfolio page for your criteria, rendered in the candidate's own template.' It also distinguishes the tool from siblings by naming get_portfolio and match_criteria as the source of the block ids rather than as alternatives, so an agent can tell this is the terminal assembly step.

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?

It states the prerequisite clearly: blocks must come 'by kind + id from get_portfolio / match_criteria', which tells the agent what must run first. It also sets a hard boundary ('You cannot add new content: unknown ids are rejected'). It stops short of naming an explicit when-not condition or what to do instead if the page already exists.

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

All made.show 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?