Skip to main content
Glama

markContentSeen

Mark content items as seen after posting to track viewing status across YouTube, blogs, and releases within the Content Fetcher MCP server.

Instructions

Mark a content item as seen AFTER posting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
typeYes

Implementation Reference

  • The handler function for the 'markContentSeen' tool. It destructures the input parameters and calls the markSeen helper function, then returns a success JSON response.
    execute: async ({ id, type }) => {
      await markSeen(type, id);
      return JSON.stringify({ success: true });
    },
  • Zod schema defining the input parameters for the markContentSeen tool: id (string) and type (enum: youtube, blog, release).
    parameters: z.object({
      id: z.string(),
      type: z.enum(["youtube", "blog", "release"]),
    }),
  • src/server.ts:181-192 (registration)
    Registration of the 'markContentSeen' tool using server.addTool, specifying name, description, input schema, and execute handler.
    server.addTool({
      name: "markContentSeen",
      description: "Mark a content item as seen AFTER posting.",
      parameters: z.object({
        id: z.string(),
        type: z.enum(["youtube", "blog", "release"]),
      }),
      execute: async ({ id, type }) => {
        await markSeen(type, id);
        return JSON.stringify({ success: true });
      },
    });
  • Helper function that marks a content item as seen by loading the last_seen data, adding the id to the appropriate type array if not already present, and saving the updated data.
    async function markSeen(type: string, id: string) {
      const data = await loadLastSeen();
      if (!data.seen[type]) data.seen[type] = [];
      if (!data.seen[type].includes(id)) data.seen[type].push(id);
      await saveLastSeen(data);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is to 'mark as seen' which implies a state change, but doesn't specify if this is idempotent, requires permissions, affects other operations, or what the expected outcome is. The timing hint ('AFTER posting') adds some context but leaves critical behavioral traits undocumented.

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?

The description is extremely concise at just one sentence with zero wasted words. It's front-loaded with the core action and includes a useful timing constraint, making it efficient and easy to parse despite its brevity.

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 mutation tool with no annotations, no output schema, and 2 undocumented parameters, the description is insufficient. It doesn't explain what 'marking as seen' means operationally, what the parameters represent, or what happens after invocation. The timing constraint helps but doesn't compensate for the broader contextual gaps.

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?

With 0% schema description coverage for both parameters, the description provides no information about what 'id' and 'type' represent or how they should be used. While the enum values for 'type' are visible in the schema, the description doesn't explain their meaning or relationship to the marking operation, failing to compensate for the schema's lack of descriptions.

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 clearly states the action ('Mark as seen') and resource ('content item'), and specifies timing ('AFTER posting'), which provides useful context. However, it doesn't differentiate from sibling tools like 'isNewContent' that might check content status, leaving some ambiguity about when to use one versus the other.

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

Usage Guidelines2/5

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

The description provides minimal guidance with 'AFTER posting', but offers no explicit when-to-use rules, alternatives, or exclusions. It doesn't clarify if this should be used instead of or in conjunction with siblings like 'isNewContent', leaving the agent to guess about proper usage contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EbonyLouis/content-fetcher-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server