Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

Get Daily Tasks

get_daily_tasks
Read-onlyIdempotent

Fetch SupaBird Daily Tasks from Home (newcomer intro package or ongoing post-trial Home) for today, or for a past day. Past days: pass date as "yesterday" or YYYY-MM-DD within the last 14 days. They are view only; tasks show as completed or missed.

When to call:

  • User asks what to do today, for their daily tasks, Home tasks, or a growth checklist.

  • Before helping them work through today's posting / engagement / coaching actions.

RESPONSE FORMATTING:

  • Present formattedText as the task list (do not replace it with a short paraphrase).

  • Then offer to help complete available tasks using other SupaBird tools (search, drafts, scheduling, performance report).

  • Only show tasks that are already in the list. Do not mention generating placeholders or ask the user to retry for personalized tasks.

  • If eligible is false, explain the message and do not invent tasks.

Do NOT mark tasks complete from this tool. Use complete_daily_task only after the user confirms they did the work, or after you finished it with them.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. "yesterday" or a date as YYYY-MM-DD within the last 14 days to see that day's tasks (view only). Omit for today.
social_setNoThe social set (brand) this is for: its name, id or one of its handles. Omit when the user has one set.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: past days are view-only, tasks render as completed or missed, the 14-day window, and the `eligible=false` handling. It stops short of describing ordering or empty-list behavior, so it is strong but not exhaustive.

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?

Purpose is front-loaded and the labeled sections (When to call, Response formatting) make scanning easy. The response-formatting block is slightly long and leans toward prompt-style guardrails ("do not invent tasks"), but each bullet addresses a real failure mode rather than padding.

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?

There is no output schema, so the description carries the return-value burden and does so: it names `formattedText` as the authoritative list and explains the `eligible` flag. Combined with the mutation boundary against complete_daily_task, an agent has everything needed to call and present results correctly.

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%, and both parameters already document the "yesterday"/YYYY-MM-DD format and the social-set name/id/handle option. The description restates the date constraint but adds no new syntax, default, or disambiguation for `social_set`, so the schema does the heavy lifting.

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?

The description opens with a specific verb and resource ("Fetch SupaBird Daily Tasks from Home") and scopes it to today or a past day. It also explicitly separates itself from the write-path sibling by stating "Do NOT mark tasks complete from this tool. Use complete_daily_task only after...", so an agent can distinguish it without opening another schema.

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?

A dedicated "When to call" block names the user intents (what to do today, daily tasks, Home tasks, growth checklist) and the sequencing case (before working through today's actions). It also gives the negative case for completion and the fallback behavior when `eligible` is false, leaving little to inference.

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

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