Skip to main content
Glama
Sign In

fillprompt

by com.fillprompt
OverviewDiscussionsAdmin

Get prompt

get_prompt
Read-only

Get the full text of one fillprompt.com prompt by its page URL or slug, with its fill-in slots, sample images or video, and credit to the original author. Fill the slots with the user's details before using the prompt, and keep the credit when you share it.

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": {
      "ref": "<ref>"
    },
    "name": "get_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe prompt page URL from search_prompts (e.g. https://fillprompt.com/prompt/...) or its slug.
typeNoHelps when a bare slug is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful return-content detail (fill-in slots, sample media, author attribution), but says nothing about failure modes such as an invalid slug or missing prompt.

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?

Two sentences, front-loaded with the retrieval semantics before the usage caveats. The second sentence is advisory rather than invocation-related, but it is short and does not bloat the definition.

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?

For a simple two-parameter read-only tool with no output schema, the description covers what is fetched and what the payload contains, which is the main gap structured fields cannot fill. Only edge-case behavior (invalid or ambiguous refs) is unaddressed.

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 coverage is 100%, so both parameters are fully documented in the schema, including the enum for 'type'. The description only restates 'page URL or slug' and adds no meaning about how 'type' interacts with a bare slug beyond what the schema already says. Baseline 3 applies 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get the full text of') and a specific resource ('one fillprompt.com prompt by its page URL or slug'), and enumerates what comes back (slots, sample images/video, author credit). It implicitly contrasts with search_prompts by emphasizing 'one' prompt, though it never names the sibling.

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?

Gives post-retrieval guidance ('Fill the slots with the user's details', 'keep the credit when you share it') but no explicit when-to-use/when-not guidance or routing to search_prompts for discovering a slug. The alternative is only hinted at indirectly via the schema's mention of search_prompts.

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

All fillprompt 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