Skip to main content
Glama
ubaranzorlu
by ubaranzorlu

fonzip_fundraising

Destructive

Manage fundraising campaigns, events, teams, and team campaigns: create, update, list, and change statuses.

Instructions

Bagis toplama: kampanyalar (fundraising campaign), kampanya etkinlikleri (fundraising event) ve takimlar (fundraising team) ile takimlara bagli kampanyalar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo[create, create_event, update_event] Fundraising campaign id
urlNo[create] campaign url
dataNo[update] key value pairs of fields and values (see example)
fieldNo[update] field to be updated. Gecerli degerler: title, image, bank_account_list, personal_message, has_target, hide_donor_list, hide_total_donation, has_special_date, phone_show, phone_required, birthday_show, birthday_required, address_show, address_required, tckno_show, tckno_required, message_show, has_target, has_special_date, target, event_date, sub_donation_type_id, payment_settings_id, thanks_mail_id, referral_thanks_mail_id, thanks_sms_id, certificate_id, referral_certificate_id, association_campaign_target_id
imageNo[create, create_team, update_team] campaign image url
queryNo[list, list_teams] search parameter. start with - (minus) char to exclude searched text
titleNo[create, create_event, create_team, create_team_campaign, update_event, update_team, update_team_campaign] Zorunlu: create_team, create_team_campaign, update_team, update_team_campaign. campaign title
valueNo[update]
actionYes[update_status] set status of fundraising campaign - reactivate: reactivate finalized campaign - finalize: finalize active campaign - featured: toggle the featured flag on the campaign (requires `featured` body field; up to 6 campaigns per association may be featured; only active campaigns are eligible)
statusNo[create, list, list_teams, update_team] campaign status <br> - 0: waiting approval <br> - 1: approved <br> - 2: rejected <br> - 3: finalized <br> - 4: deleted <br> - 5: waiting extra approval <br> - 7: archived
targetNo[create, create_event, create_team_campaign, update_event, update_team_campaign] campaign target
defaultNo[create_team_campaign, update_team_campaign] Fundraising team campaign is currently active & default
detailsNo[create_team, update_team] Zorunlu: create_team, update_team. Fundraising team description
team_idNo[create_team_campaign, delete_team, delete_team_campaign, get_team, list_team_campaigns, update_team, update_team_campaign] Zorunlu: create_team_campaign, delete_team, delete_team_campaign, get_team, list_team_campaigns, update_team, update_team_campaign.
user_idNo[create, create_team, update_team] Zorunlu: create_team, update_team. userid
campaignNo[create_team] Zorunlu: create_team.
event_idNo[delete_event, update_event] Zorunlu: delete_event, update_event.
featuredNo[update_status] Required when `action=featured`. Pass `true` to add the campaign to the Featured Campaigns block, `false` to remove it. Adding beyond the 6-campaign cap responds with HTTP 400.
how_manyNo[list, list_teams] How many records should be listed
multipleNo[update] true if updating multiple fields
order_byNo[list, list_teams] ordering
user_noteNo[create] users note
currenciesNo[create] valid currencies
event_dateNo[create] Event date
has_targetNo[create, create_team_campaign, update_team_campaign] campaign has target
phone_showNo[create] true if phone is asked
start_pageNo[list, list_teams] start page of records
tckno_showNo[create] true if tckno is asked
campaign_idNo[delete, delete_team_campaign, get, update, update_status, update_team_campaign] Zorunlu: delete, delete_team_campaign, get, update, update_status, update_team_campaign.
category_idNo[list] fundraising campaigns' donation category id
create_dateNo[list] create date filter
currency_idNo[create_team, update_team] Zorunlu: update_team. Fundraising team default Currency ID
address_showNo[create] true if address is asked
message_showNo[create] true if donors may leave a message. Ships enabled, unlike the other *_show flags
birthday_showNo[create] true if birthday is asked
campaign_listNo[update_team] Zorunlu: update_team.
thanks_sms_idNo[create] thanks sms id
certificate_idNo[create] certificate
phone_requiredNo[create] true if phone is required
tckno_requiredNo[create] true if tckno is required
thanks_mail_idNo[create] thanks mail id
create_date_cndNo[list] create date filter condition
hide_donor_listNo[create] donor list is hidden or not
address_requiredNo[create] true if address is required
has_special_dateNo[create] True if campaign has a event date like birthday, memorial day etc.
personal_messageNo[create] campaign message
team_campaign_idNo[list] fundraising campaign teams' campaign id
bank_account_listNo[create]
birthday_requiredNo[create] true if birthday is required
target_currency_idNo[create, create_team_campaign, update_team_campaign] fundraising campaign target currency id
hide_total_donationNo[create] total donations is hidden or not
payment_settings_idNo[create, list] payment system id
sub_donation_type_idNo[create] donation category id
referral_certificate_idNo[create] referral certificate id
referral_thanks_mail_idNo[create] referral thanks mail id
association_campaign_target_idNo[create, list] fundraising event id
Behavior2/5

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

The description adds no behavioral information beyond annotations: it does not mention mutation, deletion, finalization, state changes, permissions, or side effects. Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description itself does not disclose any operation semantics. There is no contradiction with annotations, but there is also no added behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is under-specified rather than appropriately concise for a 56-parameter, multi-action tool. It lacks any structure such as an action list, usage context, or key distinction hints. For this complexity level, the brevity is more a deficiency than a strength.

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?

Given a 56-parameter surface, no output schema, and multiple implied operations, the description only provides a high-level resource scope. It does not explain how actions route parameters, what operations are available, or what the tool returns. The schema carries nearly all the operational meaning, leaving the description incomplete as a standalone guide.

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 100%, so the input schema already documents all 56 parameters and their action-specific meanings. The tool description provides no parameter-level semantics and does not need to, given the complete schema. This matches the baseline 3 for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the covered resources: fundraising campaigns, campaign events, fundraising teams, and team campaigns. It is not a tautology because it enumerates these subresources, but it contains no action verb and reads as a static domain label rather than a statement of what the tool does. It does somewhat distinguish the tool from siblings like fonzip_events or fonzip_donations by naming campaign-specific resources.

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 resource list implies that this tool is for fundraising-related entities, which gives some context on when it applies. However, the description never explicitly says when to use it vs. alternatives such as fonzip_events or fonzip_donations, and it does not mention exclusions or alternative tools. Usage guidance is implied rather than stated.

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/ubaranzorlu/fonzip-mcp'

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