Skip to main content
Glama

Create prompt

create-prompt

Create a visibility prompt, the question PingAura asks AI engines on each run, for one domain. The topic is matched by name ignoring case, or created. An active prompt joins the next run and counts toward the prompt quota, so creation is refused at the quota; a draft does neither. A prompt with the same text on the domain is refused. Returns promptId, status and topicId.

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": {
      "domain_id": "<domain_id>",
      "topic": "<topic>",
      "prompt": "<prompt>"
    },
    "name": "create-prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic name (created if new)
promptYesPrompt text
statusNoactive (default) or draftactive
filtersNoCustom filter values to tag the prompt with, as key to value slug, e.g. {"product":"ill"}. The declared keys and their valid values are the ones list-prompt-filters returns. An undeclared key or value is refused, not ignored.
languageNoLanguageEnglish
domain_idYesDomain ID from list-domains
content_typeNoContent typeblog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / status / description
      Previous value: -"Prompt status"New value: +"active (default) or draft"
    • changedInput schema / properties / topic / description
      Previous value: -"Topic name (auto-created if new)"New value: +"Topic name (created if new)"
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / filters / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing the quota refusal, the duplicate-text refusal, the side effect that an active prompt joins the next run and counts toward quota, and that undeclared filter keys/values are refused rather than ignored. It also names the return fields (promptId, status, topicId), which the annotations do not cover.

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 tightly packed sentences, front-loaded with the purpose, then matching/creation rules, then quota and duplicate refusals, then return values. No sentence is redundant with the schema or padding.

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 mutation with a nested filters object and no output schema, the description covers purpose, creation/matching rules, quota and duplicate failure modes, draft vs active semantics, and the returned fields. Nothing an agent needs to call it correctly and predict the outcome is missing.

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 description coverage is already 100%, so the baseline is 3; the description adds real semantics on top — topic matching is case-insensitive and created if absent, and status determines whether the prompt joins the next run and consumes quota. It could have added a word on language or content_type effects to be exhaustive, but the meaningful parameters are clarified.

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 specific verb and resource ('Create a visibility prompt') and defines the domain concept inline ('the question PingAura asks AI engines on each run, for one domain'). An agent can tell this apart from create-prompt-topic or create-article 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 Guidelines4/5

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

Gives clear conditions: an active prompt joins the next run and consumes quota so creation is refused when the quota is exhausted, while a draft is free; duplicate prompt text on a domain is refused. It stops short of naming an explicit alternative sibling to use instead, but the decision context for active vs draft and quota is fully stated.

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