Skip to main content
Glama
Sign In

Hustlin

by ai.hustlin
OverviewDiscussionsAdmin

Approve, skip or edit an action

approve

Decide one action: approve, skip or edit its draft. Approving runs it as the product's owner and publishes or sends through the accounts connected on hustlin.ai. The founder's own post (queue_post) with a scheduledFor still ahead is the exception: approving keeps it waiting and it posts at that time (delivery scheduled, with publishAt); run posts it now. Needs the approver role or higher.

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": {
      "actionId": "<actionId>",
      "decision": "<decision>"
    },
    "name": "approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoReplacement draft text. Required for edit, optional with approve.
actionIdYesThe action id (from actions).
decisionYesapprove: ship it now (publishes or sends through connected accounts; manual tasks stay guidance). skip: don't do it. edit: change the draft without approving.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing real-world consequence (runs as the product's owner and actually publishes/sends through connected accounts), the permission prerequisite ('needs the approver role or higher'), and the scheduling variant where an approved post stays queued with a publishAt. That is exactly the authorization and side-effect context the readOnlyHint/openWorldHint flags cannot convey.

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?

Front-loaded with the decision and the three options, then the side-effect and scheduling caveats; no filler sentences. The second sentence is dense and slightly run-on, which keeps it from a 5, but every clause carries operational meaning.

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?

No output schema exists, and the description compensates by describing outcomes (immediate publish/send vs. scheduled delivery with publishAt), plus who the action runs as and who is allowed to run it. Nothing an agent needs in order to invoke this correctly appears to be 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% and the enum already documents approve/skip/edit and the content-replacement field, so the description does not need to re-explain parameters. It adds only marginal meaning (approve taking an optional content edit; the approve-on-scheduled-post nuance), which is why 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?

States a specific verb (decide) and resource (one action) plus the three possible decisions, and names the sibling tools whose behavior it differs from (queue_post, run). An agent can tell exactly what this does and how it differs from the immediate-post path without opening the 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 routing context: approving publishes/sends through connected accounts, while 'run posts it now', and a founder's scheduled queue_post is explicitly carved out as the exception. It lacks an explicit 'do not use when' for cases like manual tasks or failed connections, so it lands just 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.

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