Skip to main content
Glama
UserClimb

UserClimb

by thomaslrw

How to write like a human marketer

writing_method
Read-only

Read this before writing content ideas, hooks, scripts, carousels, or captions to prevent robotic AI-sounding copy. It gives a step-by-step human marketer method plus rules and giveaway words.

Instructions

Why AI content sounds robotic and the step-by-step method a good human marketer follows instead, plus the rules and the words that give AI away. Read this before writing any content ideas, hooks, scripts, carousels or captions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writing_method"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 safety is covered. The description adds that the payload is guidance-style content rather than data, but says nothing about size, structure, or whether the method is static across calls, leaving an agent unable to predict what arrives without a trial call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no padding, but the leading clause 'Why AI content sounds robotic' is persuasion rather than operational information, and the actionable trigger appears only at the end. Front-loading 'read this before writing hooks, scripts or captions' would serve an agent better.

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 zero-parameter, no-output-schema knowledge tool with annotations covering safety, the description gives enough to decide to call it: what it contains and when. The remaining gap is that it neither states how the guide relates to get_playbook / check_draft nor how long the returned method is.

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?

There are no parameters and no fields to disambiguate, so the schema carries no burden the description needs to compensate for. The baseline of 4 applies; no parameter meaning is missing.

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?

The description makes clear this is a reference document: a step-by-step human-marketing writing method, the rules behind it, and the words that read as AI-generated. The verb is implicit ('read this') rather than stated as a return, and it never distinguishes itself from a sibling like get_playbook or check_draft, so an agent must infer the boundary.

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?

'Read this before writing any content ideas, hooks, scripts, carousels or captions' gives a concrete trigger condition tied to specific downstream tasks. It stops short of saying when NOT to use it or naming an alternative tool, so the agent has a clear entry point but no routing rules among siblings.

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