Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_tg_resource_post_record

Record a confirmed Telegram publication link for a cataloged group or channel, updating the local audit trail without sending messages.

Instructions

Record a confirmed Telegram publication link for a cataloged group or channel. This only updates the local audit trail and never sends a message.

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": {
      "public_url": "<public_url>"
    },
    "name": "ads_tg_resource_post_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
statusNo
metadataNo
usernameNo
posted_atNo
project_idNoneron
public_urlYes
recorded_atNo
resource_idNo
moderation_statusNo
telegram_message_idNo
telegram_resource_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the most important trait: it only updates the local audit trail and never sends a message, which prevents the agent from mistaking it for a send action. It is silent on permissions, duplicate/upsert behavior for public_url, idempotency, and what the status/moderation_status values mean operationally.

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, both front-loaded with the key action and the key safety fact. Nothing is wasted and no restatement of the tool name occurs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter nested write tool with no annotations and no output schema, the description is far too thin. It establishes intent and non-sending behavior but leaves the agent unable to populate the other eleven fields correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Twelve parameters with 0% schema description coverage means the description must compensate, and it does not. It mentions only the publication link implicitly (public_url) while leaving username, status, moderation_status, metadata, project_id, resource_id, telegram_message_id, posted_at, recorded_at, and notes completely unexplained.

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 names a specific verb and resource: 'Record a confirmed Telegram publication link for a cataloged group or channel.' That is far more precise than the bare tool name. It doesn't explicitly contrast with the adjacent ads_tg_resource_upsert or ads_tg_resource_post_list tools, so sibling differentiation is only implicit.

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?

The phrase 'confirmed... publication link' implies this is called after a post has already happened, which is useful implied usage. However, there is no explicit when-to-use, no exclusion versus ads_tg_resource_upsert, and no stated prerequisite that the resource must already be cataloged besides the adjective 'cataloged'.

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

Deploy Server

Other Tools