Skip to main content
Glama

My profile activity

profile_activity_list
Read-onlyIdempotent

Recent changes to your own profile, newest first: what was changed (field names only, no values), when, and whether it was done on the website or through a connection. Pass next_cursor to get the next page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries (1-50).
cursorNonext_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: newest-first ordering, the privacy-relevant detail that only field names appear and never values, and the website-vs-connection provenance of each change. It does not say how pagination terminates (last page / empty next_cursor).

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, zero filler. The content of each entry is front-loaded and the pagination instruction is placed last, which matches the order an agent needs it.

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 read-only two-parameter list with a full schema and no output schema, the description covers what the agent needs: scope, ordering, entry contents, and how to page. Only the end-of-pagination condition and the entry limit are left unstated.

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 documented and the baseline applies. The description reinforces the cursor parameter's purpose ('next_cursor to get the next page') but adds no format or behavior detail beyond the schema, and never mentions the limit parameter or its 1-50 range.

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 gives a specific verb+resource ('Recent changes to your own profile'), states ordering ('newest first'), and enumerates exactly what each entry contains (field names only, timestamp, source channel). The 'your own profile' scoping implicitly separates it from other activity feeds, but no sibling is named or explicitly excluded.

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

Usage Guidelines3/5

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

Usage is only implied: reading recent changes to your own profile. The single directive is pagination ('Pass next_cursor to get the next page'), which is a mechanical instruction rather than when-to-use guidance. No condition tells the agent when to prefer this over the other activity or profile tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources