Skip to main content
Glama
Sign In

The Daily Workflow — AI Tools & Free Alternatives

by com.thedailyworkflow
OverviewDiscussionsAdmin

build_custom_pipeline_url

Read-onlyIdempotent

For a custom task (no existing pipeline matches), get a deep link to the Pipeline Builder on thedailyworkflow.com.

The builder composes a step-by-step pipeline from 15000+ AI tools with
ready-to-paste prompts. The MCP server doesn't run it directly — it returns
the prefilled URL where the user can run it.

Args:
    task: Description of what the user wants to accomplish. Example:
          "create a YouTube channel with bedtime stories using AI for video and voice".
    lang: "en" or "ru" (default "en").

Returns:
    Dict with builder_url (open this in browser), task (echoed), and a note explaining
    what happens.

Use this when search_pipelines returns no good match. ALWAYS call search_pipelines first
to check for existing solutions before suggesting the builder.

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": {
      "task": "<task>"
    },
    "name": "build_custom_pipeline_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: "en" for English or "ru" for Russian. Default: "en".en
taskYesPlain-language description of what the user wants to accomplish, e.g. "create a YouTube channel with bedtime stories using AI for video and voice".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds the non-obvious behavioral fact that the server does not run the pipeline at all — it only returns a prefilled URL the user opens. That is genuinely useful context an agent could otherwise misread as an execution tool. It stops short of noting URL lifetime, auth requirements, or whether the builder link persists.

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?

The opening two sentences are front-loaded with the essential routing rule and are worth their space, and the Returns block earns its place because no output schema exists. The Args section is largely redundant with the input schema, which costs a little efficiency but the document remains scannable.

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 two-parameter read-only tool with no output schema, the description supplies the routing rule, the nature of the returned artifact, the keys in the returned dict, and the fact that execution is out of scope. Nothing an agent needs to invoke it correctly is missing.

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 already fully documented, and the description's Args block restates them almost verbatim (same task example, same en/ru note) rather than adding constraints such as length limits or what happens with an unrecognized lang value. Baseline 3 applies since the schema does the work.

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 — get a deep link to the Pipeline Builder for a custom task — and immediately scopes it with 'no existing pipeline matches', which separates it from search_pipelines and get_pipeline_details. The agent knows exactly what artifact comes back (a prefilled URL, not an executed pipeline).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit trigger ('Use this when search_pipelines returns no good match') and an explicit precondition ('ALWAYS call search_pipelines first'), naming the sibling tool by name. This is the when-to-use / when-not-to-use pattern at its clearest.

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

All The Daily Workflow — AI Tools & Free Alternatives toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources