Skip to main content
Glama
carlosazaustre

Activity Reporting MCP Server

submit_content_creation

Submit content creation activity drafts to report details like title, description, date, type, metrics, and URL, ensuring accurate activity tracking for Google Developer Experts.

Instructions

Submit a content creation activity draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityDateYesDate published (YYYY-MM-DD format)
activityUrlYesLink to Content
additionalInfoNoAdditional information (optional)
contentTypeYesContent type
descriptionYesWhat was it about?
metricsYes
privateNoDo you want to make this activity private? (optional)
tagsNoTags (optional)
titleYesWhat was the title?

Implementation Reference

  • src/server.ts:80-142 (registration)
    Registration of the 'submit_content_creation' tool in the ListTools response, including detailed input schema for validation.
    {
      name: "submit_content_creation",
      description: "Submit a content creation activity draft",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "What was the title?",
            minLength: 3,
            maxLength: 200,
          },
          description: {
            type: "string",
            description: "What was it about?",
            maxLength: 2000,
          },
          activityDate: {
            type: "string",
            pattern: "^\\d{4}-\\d{2}-\\d{2}$",
            description: "Date published (YYYY-MM-DD format)",
          },
          contentType: {
            type: "string",
            description: "Content type",
            enum: Object.values(ContentType),
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Tags (optional)",
            minItems: 0,
          },
          metrics: {
            type: "object",
            properties: {
              readers: {
                type: "integer",
                minimum: 1,
                description: "How many people read your content?",
              },
            },
            required: ["readers"],
          },
          activityUrl: {
            type: "string",
            maxLength: 500,
            pattern: "^https?://.*",
            description: "Link to Content",
          },
          additionalInfo: {
            type: "string",
            maxLength: 2000,
            description: "Additional information (optional)",
          },
          private: {
            type: "boolean",
            description: "Do you want to make this activity private? (optional)",
          },
        },
        required: ["title", "description", "activityDate", "contentType", "metrics", "activityUrl"],
      },
    },
  • Input schema definition for the submit_content_creation tool, specifying properties, types, constraints, and required fields.
    {
      name: "submit_content_creation",
      description: "Submit a content creation activity draft",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "What was the title?",
            minLength: 3,
            maxLength: 200,
          },
          description: {
            type: "string",
            description: "What was it about?",
            maxLength: 2000,
          },
          activityDate: {
            type: "string",
            pattern: "^\\d{4}-\\d{2}-\\d{2}$",
            description: "Date published (YYYY-MM-DD format)",
          },
          contentType: {
            type: "string",
            description: "Content type",
            enum: Object.values(ContentType),
          },
          tags: {
            type: "array",
            items: { type: "string" },
            description: "Tags (optional)",
            minItems: 0,
          },
          metrics: {
            type: "object",
            properties: {
              readers: {
                type: "integer",
                minimum: 1,
                description: "How many people read your content?",
              },
            },
            required: ["readers"],
          },
          activityUrl: {
            type: "string",
            maxLength: 500,
            pattern: "^https?://.*",
            description: "Link to Content",
          },
          additionalInfo: {
            type: "string",
            maxLength: 2000,
            description: "Additional information (optional)",
          },
          private: {
            type: "boolean",
            description: "Do you want to make this activity private? (optional)",
          },
        },
        required: ["title", "description", "activityDate", "contentType", "metrics", "activityUrl"],
      },
    },
  • Core handler logic that performs the HTTP POST request to the Advocu GDE API to submit the content creation activity draft, handles errors, and returns formatted response content.
    private async submitActivityDraft(
      endpoint: string,
      data:
        | ContentCreationDraft
        | PublicSpeakingDraft
        | WorkshopDraft
        | MentoringDraft
        | ProductFeedbackDraft
        | GooglerInteractionDraft
        | StoryDraft,
    ): Promise<{
      content: Array<{
        type: string;
        text: string;
      }>;
    }> {
      const url = `${this.baseUrl}/activity-drafts/${endpoint}`;
    
      try {
        const response = await fetch(url, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${this.accessToken}`,
          },
          body: JSON.stringify(data),
        });
    
        if (!response.ok) {
          const errorText = await response.text();
          let errorMessage = `GDE API error (${response.status})`;
    
          if (response.status === 401) {
            errorMessage = "❌ GDE authentication failed. Your ADVOCU_ACCESS_TOKEN may be expired or invalid.\n\nPlease check your Advocu access token configuration.";
          } else if (response.status === 400) {
            errorMessage = `❌ GDE API rejected the request:\n\n${errorText}\n\nPlease check:\n- All required fields are present\n- Field values match expected formats\n- Tags are valid\n- Date format is correct (YYYY-MM-DD)`;
          } else if (response.status === 429) {
            errorMessage = "⏱️ GDE API rate limit exceeded (30 requests/minute). Please wait and try again.";
          } else {
            errorMessage = `❌ GDE API error (${response.status}):\n\n${errorText}`;
          }
    
          // Return error as content instead of throwing
          return {
            content: [
              {
                type: "text",
                text: errorMessage,
              },
            ],
          };
        }
    
        const result = (await response.json()) as Record<string, unknown>;
    
        return {
          content: [
            {
              type: "text",
              text: `✅ GDE Activity draft submitted successfully!\n\nEndpoint: ${endpoint}\nStatus: ${response.status}\nResponse: ${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        const errorMsg = this.getErrorMessage(error);
        throw new McpError(
          ErrorCode.InternalError,
          `❌ Failed to submit GDE activity:\n\n${errorMsg}\n\nEndpoint: ${endpoint}`
        );
      }
    }
  • Dispatch case in the MCP tool call handler that routes 'submit_content_creation' invocations to the submitActivityDraft method with the specific 'content-creation' endpoint.
    case "submit_content_creation":
      return await this.submitActivityDraft("content-creation", args as unknown as ContentCreationDraft);
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. 'Submit a content creation activity draft' implies a write/mutation operation but provides no information about permissions required, whether submissions are final or editable, response format, or any system constraints. Significant behavioral context is missing.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after submission, whether there are validation rules beyond schema constraints, or how this tool differs from sibling submission tools. The high schema coverage helps but doesn't compensate for missing behavioral context.

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 description coverage is high at 89%, so the schema already documents most parameters well. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score for good schema coverage.

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 ('submit') and resource ('content creation activity draft'), making the purpose immediately understandable. It doesn't distinguish from sibling tools, but the specific focus on content creation is evident.

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?

No guidance is provided about when to use this tool versus the six sibling submission tools (submit_googler_interaction, submit_mentoring, etc.). The description offers no context about appropriate use cases or prerequisites for content creation submissions.

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

Related 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/carlosazaustre/advocu-mcp-server'

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