Skip to main content
Glama
Sign In

fnlowl

by com.fnlowl
OverviewDiscussionsAdmin

List projects

list_projects
Read-only

Lists the projects this credential can act on. A project is one site or brand under the account, and every widget, lead, campaign and sequence belongs to one. Every other tool takes an optional project argument: pass one of these ids to run that call in that project. Without it, a call uses the connection's project (the row with current true) or, when no row is current, reads across the whole account. When there is more than one row and none is current, ask the user which website they mean and pass its id on each call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real context the annotations cannot convey: the default project resolution logic and the cross-account read behavior when no project is current, which materially affects how an agent interprets downstream call results.

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 core purpose, then the definition, then the default-resolution rules, then the ambiguous-case instruction — a logical progression. It is on the longer side and the mid-sentence parenthetical about the 'current true' row is slightly dense, but no sentence is filler.

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?

With no output schema, the description still conveys the shape of the result (rows, one of which may be 'current') and the credential scoping, so an agent can act on it without guessing. For a zero-parameter roster tool this is as complete as needed.

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 zero parameters, so the baseline is 4 and there is nothing in the schema to clarify. The description does add value by explaining that the returned ids are consumed as the optional project argument of every other tool, giving the output rows meaning as inputs elsewhere.

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 ('Lists the projects this credential can act on') and immediately defines what a project is ('one site or brand under the account'), which differentiates it from create_project and the other sibling list_* tools. An agent knows exactly what this returns.

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?

Goes well beyond when-to-call by explaining how the returned ids feed every other tool ('pass one of these ids to run that call in that project'), the fallback resolution rules (current row vs. whole-account read), and the explicit escalation path when multiple rows exist and none is current: ask the user which website they mean.

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

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