Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Skill: conversion optimization

get_skill_conversion_optimization
Read-onlyIdempotent

The optimize loop: turn a weak analytics signal into ONE concrete page edit, republish, and measure the delta. Symptom→cause→fix playbook for low conversion, high bounce, scroll drop-off, weak CTA. Load after reading analytics, before editing to improve performance.

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": "get_skill_conversion_optimization"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish this is a safe, idempotent, non-destructive read, and the description's 'Load...' framing is consistent with that. However, phrases like 'republish, and measure the delta' describe mutating steps the tool itself does not perform, which risks an agent expecting side effects; the description also doesn't say what is returned (playbook text vs. structured steps), leaving the read payoff underspecified.

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?

Two sentences, front-loaded with the content and followed by the sequencing rule; every clause (symptoms listed, load ordering) carries information an agent needs to pick this tool. No filler.

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, read-only skill loader with no output schema, the description covers what content it supplies and when to invoke it. The remaining gap — what the returned guidance looks like — is minor but not fully closed by any other structured field.

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?

The tool takes no parameters, so the baseline is 4; the description correctly introduces no parameter expectations and requires no input semantics.

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 states the resource (a conversion-optimization skill/playbook) and its content shape — 'symptom→cause→fix playbook for low conversion, high bounce, scroll drop-off, weak CTA' — which distinguishes it from adjacent skills like get_skill_analytics or get_skill_best_practices. The verb is only implied ('Load'), and the opening 'turn a weak analytics signal into ONE concrete page edit, republish, and measure the delta' describes a workflow more than the tool's own action, which blurs what calling it actually does.

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?

It gives an explicit ordering rule: 'Load after reading analytics, before editing to improve performance,' which tells the agent both a precondition and a downstream step. It stops short of naming competing siblings (e.g., when to prefer get_skill_best_practices instead), so the routing is directional but not fully disambiguated.

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

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